Android Development

10 readers

1 users here now

Welcome to the programming.dev Android development community!

The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License

founded 1 year ago

MODERATORS

erlingur@programming.dev

will@programming.dev

Ategon@programming.dev

What ecosystem should I use if i want to make an app and not write boilerplate all day? (nerdbin.social)

submitted 1 year ago by eh@nerdbin.social to c/android_dev@programming.dev

7 comments fedilink hide all child comments

The "native" Android ecosystem has grown way too over-complicated for my liking. I do not want to dependency inject a Reactive ViewModel Room Repository DAO Purpose Factory (without blocking the main thread), I just want to make a god damn app.

My current wishlist is:

Be reasonably efficient (we're working with phones here)
Be completely open source (i.e. I should be able to throw my app on F-Droid when it's ready)
Have a not terrible implementation of Material 3/You
Don't be too "janky" for the end user (sorry, PWAs)
Be reasonably mature

What does this leave me with? Flutter? React Native?

you are viewing a single comment's thread
view the rest of the comments

[–] kabat@programming.dev 2 points 1 year ago (1 children)

Qt QML works for me. It's declarative, easy to learn, looks good, you can write logic in JavaScript, or have your code on the backend in C++, or Python with PySide. You can easily iterate on the desktop and run the exact same app on the phone, or TV. It's fast too. And given you want to go open source, licensing is not a headache (unlike closed source on LGPL Qt).

Generally it's been my UI of choice for years and I'm pretty happy with it, now with excellent Python support even more so (though I don't know how, or even if, it's possible on mobile).

[–] lightsecond@programming.dev 1 points 1 year ago

Cool. Does Qt have Material You compatible components?