4 ms·
I've done a little Android programming over the years ever since the first beta SDK (m3) hit in November 2008. Android Studio was a revelation, but like I said,
by Andrex 10y ago
I've done a little Android programming over the years ever since the first beta SDK (m3) hit in November 2008. Android Studio was a revelation, but like I said, I do very little native programming and a lot of Web stuff. I haven't messed with iOS yet.
My experience is: finally, I can program like I do on the Web! And not just in the sense it uses JS, but like, double typing R to "reload" the app being super fast and seamless. Coding my first React Native app has been the most enjoyable experience I've had creating a native mobile app ever. Even small stuff like being able to use the Fetch API over whatever native gobbledegook API Android uses is a massive quality of life improvement for me.
I actually don't particularly care for React itself (the Web version), but that's because its download/execution costs are still iffy for me and I don't think JSX has a place on the web long-term. I also don't think it's opinionated enough and the roster of React "plugins" reminds me of the bad side of jQuery widgets. (If you couldn't tell, I've moved to being more of a Vanilla JS purist in recent years as the ECMAScript standard has evolved.)
With React Native though, none of those points really matter and I'm able to enjoy the "breakthrough" of self-contained JavaScript components combined with super fast debug iterations. It's a win-win in my eyes.
- spicyj 10y agoCurious: why is JSX on web worse than on native? And if you're overwhelmed by React "plugins", we certainly suggest you not use them. Most of them are just components you can write yourself.