i recently tried to create my own app for personal use (not for upload to google play )

and boy....this thing drains my soul dry

android sdk releases new updates so quickly , that its difficult to keep track of all the versions. android studio is bulky and consumes a lot of memory.

so i tried out react native and expo instead... big mistake

since react native libraries and modules maintained by freelancers, many of them uses depreciated APIs but was not updated in the libraries, rendering them completely useless, and you wont find out after you npm installed and then find out it gives you an error deep inside its inner workings of the code.

and react native and expo libraries do not mix, you cant link them both together.

and then theres always this very annoying thing called "npm ERR! Conflicting peer dependency"

its also annoying that expo:build has been retired this year jan, my old repo of expo cant work under this eas build, it gave me some error i cannot resolve. so the code pretty much useless now

ive spent weekends trying to crack this thing.

is this part of the normal learning curve or do i have unrealistic expectation of mobile development?



This post has been edited by 15cm: Mar 24 2023, 05:29 PM

IMHO, backward compatible is very important.

You could use old tool to build app which could run from old to new version devices.

Newer version tool may have a lot of new features, but only useful if you really use it.

This is normal.