11–20 of 243 posts
I'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 appr…
- The components for iOS look nice, but some things are off: Sheet modal is weird. Animation of modals or side panels feel too slow.
- There are no animations when navigating forward or backwards.
- The demo has scrolling issues on iOS Safari and doesn’t always show the header.
- Unfaithful communication: it claims to give you native look and feel, which can never be true for HTML/CSS-based UIs that merely replicate native components.
- I see no point in using this instead of Ionic, because Ionic has the same or more components with less bugs, because it has been around a lot longer.
I'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 appr…
The project has basically 4 parts:
- 1 for the CSS parts: basically a DSL to define a giant tree of Tailwind CSS class properties, with some conditionals to take care of the context (iOS vs. Material) and other optional features.
- 3 for the React/Vue/Svelte components. They seem to provide the same features, each implemented independently.
There is definitively a separation of concern between style and behavior, so the style part could be reused in other frameworks.
But there is also a "DRY" violation with the 3 independently developed framework-dependent parts. Could this be improved by having a framework-independent part (you suggest Web Components, what would be the easier way to get this part done?) and framework-dependent adapter, or would this extra layer of indirection make things harder to understand?
I'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 appr…
React doesn't do Web Components, the community is pretty much against them.
We're looking to find the lowest common denominator of expressing UI components and thinking about JSON metadata instead of Web Components. With this, we'd have to implement some adaptor that maps JSON to each UI library, but in our case we really only have to worry about React and Native Mobile.
I'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 appr…
I'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 appr…
Because web components suck and are an overkill for what should really be the job of Scoped CSS (now indefinitely delayed because of web components)?
I 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 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 appr…
React doesn't do Web Components, the community is pretty much against them.
My 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.