r/FlutterBeginner • • 4h ago

Would you use a React Bits like component discovery platform for Flutter?

I've been thinking about this problem recently.

In the React ecosystem, projects like React Bits offer a great experience for discovering UI components. You can browse different components, see them in action, experiment with their customization options, and explore their source code.

I'd love to see a similar kind of discovery experience in the Flutter ecosystem.

Currently, when I need a UI component, my workflow is usually to search for a package, read its README, look through screenshots or examples, install it, wire it up, and only then discover whether it actually fits my project.

That's the experience I'm exploring with Widgetry.

The idea is to create a shared platform where different Flutter developers can publish their own reusable components. Other developers can discover components from different authors, interact with live previews, experiment with the customization options exposed by the author, and evaluate components before deciding to use them.

This is a little different from tools like Widgetbook, which focus on building and exploring playgrounds for your own widgets. I'm more interested in the shared discovery and publishing experience across independent component authors.

But before going too far with the idea, I'd like to understand how developers currently approach this.

  1. When you're looking for a UI component, how do you evaluate it before adding it to your project? Do you rely on screenshots, documentation, example apps, or something else?

  2. Have you ever installed a UI package and later removed it because the component didn't fit your requirements? What was missing or different from what you expected?

  3. If a component had a live interactive preview, what would you want to experiment with before deciding to use it?

I'm building Widgetry, so I'm obviously biased toward the idea. But I'd rather discover that developers don't need something like this than build a platform nobody wants.

I'd genuinely appreciate hearing about your actual experiences, including if your current workflow works perfectly well.

3 Upvotes

2 comments sorted by

1

u/Markaleth 4h ago

I believe dartpad and the flutter official component library address this already.

I personally dislike adding UI component libraries to my apps.

The way things usually go when i create an app are:

  • what flows do i have

  • what would the screens look like

  • what's the theme

  • what are the components that i need to make for those flows for my app to be coherent.

So i try to build a design system starting from some UX prototype vs pick a library that kind of funnels or forces me into a given look. Creating UI is cheap, in any case, with ot without AI, so it never feels like overhead i have to deal with.

I'd add that i generally dislike adding external libraries that address trivial / low complexity stuff because in actuality you're paying with security for convenience, especially with all the security vulnerabilities goong on lately.

2

u/Local_Opposite7752 3h ago

I think there's a bit of a misunderstanding about what I'm trying to build here.

I'm not trying to create another general-purpose UI library to replace Flutter's Material or Cupertino widgets, or something that developers have to adopt for their apps.

Those already provide the essential building blocks, and building your own design system around your application's UX is completely valid.

What I'm exploring is more of a shared discovery and publishing platform for custom Flutter components.

For example, Flutter already provides a standard TimePicker. But what if you want something more creative, like an animated circular time picker, a custom clock interface, or some other unique interaction that isn't available out of the box? You might build that yourself because you couldn't find something that fits your needs.

Widgetry would give you a place to publish that component so other developers can discover it, see it working through a live preview, experiment with its customization options, and decide whether they want to use it.

There are already plenty of interesting packages on pub.dev, but evaluating them can sometimes mean going through documentation, installing the package, and running example code just to understand how the component actually looks and behaves.

That's the experience I'm interested in improving.

And I agree with your point about dependencies and security. I don't think developers should add unnecessary packages just for convenience. Making dependencies and implementation details visible is also important.

The idea isn't to replace anyone's design system or dictate how they build their apps. It's simply to make it easier to discover and share creative, reusable Flutter components.