Android Development

556 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 2 years ago

MODERATORS

erlingur

will

Ategon

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 [email protected] to c/android_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

[–] balder1993 1 points 1 year ago* (last edited 1 year ago)

If you’re writing code for yourself, you don’t need to follow the trendy stuff. Native Android can be pretty straightforward if you stick to XML and plain old MVC architecture.

If you want to build an open source app that you don’t want to have maintenance headaches it seems the best future-proof choice.

React Native has a dependency hell problem, and Flutter, well… might be a good choice but with companies cutting costs and the history of Google I don’t know if they will keep throwing money at it to make sure its development keeps on pace. Creating a framework such as Flutter requires a lot of constant effort to catch up with all the supported platforms, reason why there isn’t many similar alternatives.