[kitsunesoba]

This is one of the reasons that as a one person mobile team, I’ve avoided anything but native mobile toolkits. It’s a little more work in some ways that way, but if I have to set one platform down for a while to focus on the other, picking it back up isn’t ever a problem, and if I run into issues usually others have too and they’re easy to fix. Even the mess that are native Android projects are usually reasonable to get up to speed.

Cocoapods in particular is a huge pain in the ass though, even on native iOS projects. It’s been blissful to drop it in favor of Xcode’s built in Swift Package Manager.

As an aside, I’ve found it similarly frustrating to try to get old Rails projects running again. Found one that I hadn’t worked on in at least a decade, would be neat to see it booted up again right? Haha nope forget it, isn’t happening.

[pdntspa]

I recently got a Rails 4 project I wrote back in 2016 running on a VM for some consulting I'm doing. The contractee is still running it in production.

It was a bit of an adventure, but it can be done. The tricky thing is making sure native compilation works.

[pjmlp]

Yep, Borland always having to catch up to Windows SDKs taught me the same.

Platform tooling only.

[amateurInAll]

Thanks for sharing this. I think you nailed it: the promise of RN is very appealing to the one person mobile team but ends up being more challenging in the end.