Konsta UI – Mobile UI Components Built with TailwindCSS
1–10 of 243 posts
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#2I'm both impressed and very confused by this project.
Looking through the source code, they reimplemented all components for react, Vue and svelte. That's an impressive amount of work.
What confuses me is why they would do that... Why not just use Web Components as the core?
If you want clean integration with a framework, a small "glue" wrapper component should be easy.
I question whether the current development approach is maintainable.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#3I originally thought it was something like DaisyUI but for React Native with NativeWind, but this seems quite different, and almost a little strange haha.
I'm very impressed by the polish of the project but am curious about the main use case for a library like this.
(I guess, in what situation would one want a webpage to feel like a system native app? Potentially this paves the way for PWAs?)
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#4My startup team is working on a new project and elected Tailwind this week. Konsta looks like a great fit as we want to work well on mobile.
Wondering if there are plans to add a grid with drag+drop? We're looking to emulate the iOS homescreen where you have a grid of Icons that can be dragged/dropped using https://shopify.github.io/draggable. Having an integrated solution would help us avoid haphazard glue code.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#5I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl...
better than css or even css in js
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#6I originally thought it was something like DaisyUI but for React Native with NativeWind, but this seems quite different, and almost a little strange haha. I'm very impressed by the polish of the project but am curious about the main use case for a library like this. (I guess, in what situation would one want a webpage to feel like a system native app? Potentially this paves the way for PWAs?)
> I'm very impressed by the polish of the project but am curious about the main use case for a library like this.
I'd be very interested in something like Tamagui (https://tamagui.dev/) but for Tailwind. I tried Tamagui but it's a bit too complicated when it comes to styling and layouts.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#7I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js
I don't write CSS (normally) and yet I understand every single statement, and can easily find which statement I'd need to change for a given. It's that simple.
You could argue "well you should learn CSS!" but at the end of the day, I don't need CSS often enough to want to bother. Frameworks like TailwindCSS have been great for people like me.
-
Also you went and dug into its guts to find the implementation details, the actual usage is nowhere near that complicated: https://github.com/konstaui/konsta/blob/master/kitchen-sink/...
I can't even imagine what raw CSS lovecraftian horror captures all of the corner cases the classes you linked are hiding away from me (and to be clear, I'd rather not know or care)
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#8Anyone notice all the gambling sponsors? Looks like they're fed from OpenCollective (see BACKERS.md in the github repo). Feels like they're trying to get backlinks as their URLs end up as anchor tags on the site
Such a weird ecosystem the sponsorships have created. I see a lot of other sites with irrelevant sponsors and non-trivial amounts of money, there just for the SEO/ranking
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#9I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js
If you compare a given snapshot of code containing utility css vs well defined CSS, then yes, it looks worst.
The reality is that if the codebase and style code is in flux, that idealized CSS stylesheet will churn towards a being a mess of tech debt. Utility CSS contain redundancies (on the HTML side of things), but the rule of dumb is that you shouldn't refactor redundancies until you are absolutely sure what the unit of abstraction / isolation should be. In the case of prototype and fleshing out your designs, having a concise CSS stylesheet won't work, especially if you work with other people who are tunnel visioned on one specific scenario (a sort of tragedy of the commons) and not thinking hollistically as you would as an solo developer. We can think of that idealized, perfectly concise, stylesheet an "unstable saddle point" whereas utility CSS is not already at the saddle point but it does converge towards a stable one.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#10I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js
I don't write CSS (normally) and yet I understand every single statement, and can easily find which statement I'd need to change for a given. It's that simple. You could argue "well you should learn CSS!" but at the end of the day, I don't need CSS often enough to want to bother. Frameworks like TailwindCSS have been great for people like me. - Also you went and dug into its guts to find the implementation details, t…
Interesting, I write CSS and react/js all the time, and I don’t understand a bit of that usage example.