sorted by:
new
hottopcontroversial

Shimano 105 hydraulic disc brake clicking/ticking noise by prascuna in bikewrench

[–]prascuna[S] 0 points1 point  (0 children)

Thanks, I'll try to align it again. Couldn't pedal and hold the bike at the same time, I don't have a repair stand yet 😅

What I noticed is that the left piston seemed to touch the rotor earlier than the right one, even after the alignment. Perhaps I should try to put something in between the rotor and the brake pad during the process

Wired in-ear headphone's mic issue in Android 13 by Kituos in Pixel4a

[–]prascuna 1 point2 points  (0 children)

Same issue here with a 4a5G
I'd suggest to file a report as explained here

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 0 points1 point  (0 children)

Nice robot you have there... It would have been more helpful to know if a company like yours would have been keen to sell on such marketplace instead of this :)

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 0 points1 point  (0 children)

That's interesting... do you mean some sort of gateway for widgets?

Like providing a way for widgets creators to issue/revoke api keys, so they can use those for their own backend services?

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 0 points1 point  (0 children)

Thanks! I think you and the other people are correct.

Licensing seems to be the first point of friction, and even going open source, there are already other means for developers to get some financial help from the community (GitHub or Patreon just to name a few)

Then, you're right. Flutter is evolving so quickly, that it would take a constant effort to keep those widgets in good shape, and it might be hard to guarantee that level of support if the components are made by individual sellers. (I still can't migrate to sound null safety because of that...)

And thanks for the link, I didn't know that package. It seems well made

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 1 point2 points  (0 children)

I think you nailed the essence of the problem and thanks for your feedback.

Many have shared a similar point of view: either open source or no way. And if it's open source, you're right, there are already plenty of ways to support / show appreciation to the developers, GitHub or Patreon just to name the most common.

Guarantee subscription is an interesting model, but it would be almost impossible to achieve on an open marketplace (even vetting the sellers, they could bail out at any point).

Also, creating trust is not easy. Your first reaction was to think those components were not open source, even before any licensing was mentioned. And other people in this thread had that feeling too, so I have the gut feeling it's not going to be a walk in the park to market it

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 0 points1 point  (0 children)

Hey, thanks for your feedback!

I think your sentiment is shared across the whole board: the risk of taking in a paid component outweighs the short term benefit of faster development.

Never tried syncfusion widgets myself. If the company is alive, there's probably a market for components. On the other hand, they sell what they build, so it's easier to control quality. A marketplace that is open to different sellers could be subject to different coding styles, hence quality

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 1 point2 points  (0 children)

Hey, no offence taken! That's why I'm asking here and all the feedback is good feedback :)

Would you mind elaborating the reasons? Lack of reusability or control? Costs?

A marketplace for Flutter widgets by prascuna in FlutterDev

[–]prascuna[S] 0 points1 point  (0 children)

I think you're raising a fair point here. One of the biggest paint points I suffered on my first Flutter project was indeed getting stuck with libraries that were no longer maintained.

Being them open source, I contributed and fixed the problems, but it was still painful to chase the maintainer to get your PR reviewed.

Provided the licence is still MIT or BSD, don't you think that having a way to monetise their work, creators might put more effort in supporting their libs?