Exactly!
This looks great - the docs are fantastic and I love the focus on usability. Once you add more stateful components, like data tables and comboboxes/autocompletes (with customizable slots), Iāll probably adopt it for my own projects. Hereās the gold standard UI framework in the Vue.js world, if you want some ideas: Vuetify ā A Vue Component Framework
Edit: We would like to give it a whirl at work, but it looks like thereās no free trial. Would you consider adding one? Adopting a UI framework is a substantial undertaking, and Iād assume that most people would want to explore it first to see if it would fit their needs.
I disagree about the free trial. The price is a one time payment, so low investment if youāre actually building something.
Furthermore the docs showcase everything really well. What would you learn from a free trial.
Lastly, how would you implement free trials in a good way? There would also be no good way of revoking access.
Respectfully, Iāll keep it short to avoid a huge derail. I do appreciate that itās a one time payment rather than a monthly one, yes. But Iāve lost count of the number of libraries and frameworks where the docs promise rainbows and unicorns and it doesnāt work well (or at all) in practice, for whatever reason. Being able to try it first eliminates that risk, which IMHO is important for a brand new framework that is striving for adoption. I understand and appreciate the points youāve made, though.
You can actually try without risk. This is the refund policy
If youāre not satisfied with Fluxon UI, you can request a refund within 7 days of purchase by emailing support@fluxonui.com.
Edit: btw, Iāve bought a licence a while back. Only using it for one component so far, but everything went smoothly and worked well.
The library looks great. Any chance of releasing the roadmap of it? I see there are still few basic components missing so I am not sure about spending my money on this without knowledge of the general direction and at least some approximate time range of feature release.
I got this library as well and Iām pretty happy with it. Looks awesome and itās easy to work with.
I spent a couple of days trying out the few open source libs out there but they all had their quirks and stuff not going smoothly here and there, and/or not receiving updates for a long time. Which is perfectly fine, open source is hard work and anyone putting out there their projects for others to use is awesome.
I decided to get this after all the good opinions from this forum and checking out that the author is still actively adding new components. Iām also betting on it not being abandoned right after I bought it
Fluxon UI creator here. Iām really glad to hear youāre enjoying it!
Yes! Fluxon UI is pretty much what Iāve been doing full time currently. So you can definitely expect new components, bug fixes, enhancements and more coming.
You can double your bet on that one! As I mentioned, this is my full-time work now, so itās far from being abandoned. What I can foresee is that I probably wonāt be able to work on Fluxon UI full time forever as itās not sustainable by itself, but this only means progress might not be as fast as it is today - not that it will be abandoned.
Hey @drogovski, sorry I havenāt replied you before! For some reason I lost track of your comment.
About the roadmap: I donāt really have a roadmap. I mainly focus on things the users suggest or provide feedback on plus some other ideas I have. Since your comment, Iāve added the Autocomplete, Date Picker (with time and range pickers too) and docs, along with some bug fixes and other improvements. Right now Iām working on making Fluxon UI compatible with TailwindCSS 4 (and also getting it ready for the upcoming Phoenix 1.8) and some ādemo appsā that I will also offer to the users.
I would love to know what components you had in mind here!
Love to hear youāre updating it to tailwind 4. Iām already using that and Iām keeping around a config.js just for fluxon.
A thing Iād like to have ready to use just because Iām lazy is a bento grid. I like them a lot but I figure they would be highly specific to landing pages and probably not that hard to make anyway⦠so yeah I donāt know how much priority theyād take.
Something that would actually be good to have is a file upload input, perhaps a variant of the input component.
Looking at the pricing plan, if I collude with 14 other independent devs, we could all have a user license on the Enterprise Plan, which would be 70% cheaper for each of us. Would that be unethical? I will not pursue it if so.
Itās clearly for one organisation. So yes doesnāt sound really ethical to me. But it might be a good idea to make this clear in terms and conditions.
I mainly focus on things the users suggest or provide feedback
If you say so I tried autocomplete and it works and looks great! But I wanted to change text color and couldnāt. Could that be configurable? For now I just copied the component locally and changed the text coloring there.
Or maybe thereās a better way, idk
edit: I noticed a change when I added dark mode, I guess itās fine.
Wow. The attention to detail is remarkable. And the built-in accessibility alone is super-compelling.
FWIW, I would pay (quite a bit) more for a license that gives access to the full source, simply as a safeguard in case youād stop offering the library, and to be able to look at the source if thereās a problem.
Thanks!
Itās not exactly the āsource codeā, but you can access all the code in ./deps/fluxon
folder (including the non-minified JS), which means you could already copy everything to your project and run Fluxon independently if you want.
@andrielfn Have you ever considered accepting contributions to the library? With more people - there would be more components implemented. I would happily write a couple of components and hand it over to you so that it becomes a core Fluxon component.
Wonderful! I just bought a license.
@andrielfn is the website down? Iām trying to access it but I donāt think itās a problem on my end
works for me
update: oops, thought it was a recent comment