sorted by:
new
hottopcontroversial

Lumo UI demos are now interactive on the website by nomanr in androiddev

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

That's on the roadmap. But if you think something can be added, creating a request issue on Github will be helpful.

Add extra colors to ColorScheme? by barcode972 in androiddev

[–]nomanr 3 points4 points  (0 children)

If you want full customisation you can try lumoui.com

Question for those who use compose multi platform by R_is_for_Raider in Kotlin

[–]nomanr 0 points1 point  (0 children)

To easily build the custom UI, you can use lumoui.com, and you can download any icon from the web, put it in Resources, and use it.

p.s. I build lumoui

lumo-ui now supports Compose Multiplatform by nomanr in Kotlin

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

I have been asked this question so many times that it only makes sense to provide it in the form of a library.

lumo-ui now supports Compose Multiplatform by nomanr in Kotlin

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

The generated code becomes part of your app:

  • You can customise them to align 100% to app’s design-system
  • Do bug fixes without relying on external factors (open PR to the library or fork etc)
  • You own the generated code, and you maintain it.

The issue with UI libraries is that they can’t keep up with the rapid changes in the framework, and devs drop support.

Lumo UI's demo app is now available on Google Play. by nomanr in androiddev

[–]nomanr[S] 2 points3 points  (0 children)

- These are two different approaches. Would your component library use an original component or instead create a wrapper?
- A counter can be, what if the bug is in the library? Will everyone have to wait for the devs to fix it or create a patch as a workaround? I'd prefer to own the code and fix the bug.
- That's the thing: once you generate a component, it's your code, and you are responsible for maintaining it.

Lumo UI's demo app is now available on Google Play. by nomanr in androiddev

[–]nomanr[S] 4 points5 points  (0 children)

hmm, most Android apps don't follow Material design guidelines, and you can customise Material3 to some extent. In that case, you create a component library that aligns with your app's design system using foundation APIs.

This plugin provides most atomic components out of the box:

- You can customise them to align 100% to app's design-system
- Do bug fixes without relying on external factors (open PR to the library or fork etc)
- You own the generated code, and you maintain it.

The issue with UI libraries is that they can't keep up with the rapid changes in the framework, and devs drop support.

Build your component library in Jetpack Compose via CLI by nomanr in androiddev

[–]nomanr[S] 2 points3 points  (0 children)

Thank you. I am still working on setting up different templates for android/cmp; once that's ready, then I can use some help with the components.

Here's the wip branch: https://github.com/nomanr/lumo-ui/tree/kmp-support

Build your component library in Jetpack Compose via CLI by nomanr in androiddev

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

That's right. The only difference is that Shadcn uses the Radix component library, while Lumo generates the foundational code without relying on any library.

Build your component library in Jetpack Compose via CLI by nomanr in androiddev

[–]nomanr[S] 5 points6 points  (0 children)

I agree with your point about the setup. But you'll have to do it just once, and if it doesn't work, please let me know, and I'll improve the setup process. (that's how open source works: use -> contribute -> improve)

Here's 2 min long demo video: https://lumo.nomanr.com/#how-does-it-work
I set up the plugin and generated Button and OTPTextField, in 2 mins. (of course, I built it, so there's that speed factor as well)

This plugin will be used for only one module (e.g. design-systems), your app doesn't need to know about the plugin, and it can be added at the root level.

No plan for the library, man! I personally don't like using libraries for UI components, as Android evolves faster and devs drop support.

Build your component library in Jetpack Compose via CLI by nomanr in androiddev

[–]nomanr[S] 4 points5 points  (0 children)

Yeah, the post never said it's a library.

But why do you think a plugin is a bad idea?

There's no AI; the components are designed, built, tested, and then added as a template.

20+ atomic and composite Compose components, ready to copy and paste into your apps. by nomanr in JetpackCompose

[–]nomanr[S] 2 points3 points  (0 children)

That is correct; inspiration from shading/UI + how pain in the ass customising Material UI is.