,
7 tweets,
2 min read
Read on Twitter
In my consulting work, I've had several clients go down the cross platform path, only to have to start over and rewrite native from scratch. I've had a few who were modestly successful with cross-platform, and I'll discuss those too. 1/
In the cases that failed, the proximate cause has most commonly been performance (particularly various kinds of glitching). All of my clients who went cross platform have required substantial "if iOS…else if Android…" code that substantially degraded the value promise. 2/
Several of my clients said "performance doesn't really matter for us." One was explicit that their users were required to use the app, so it didn't matter. (!!!) They always actually meant "…as long the performance is good enough." That's the same as "performance matters." 3/
Same with tight platform integration. Doesn't matter…except the pieces you want…and those matter a lot. Everyone eventually needs a lot more features than they think they will for "just a simple app." 4/
That said, I've seen cross-platform frameworks be relatively successful. In all those cases, the team had deep native skills *and* at least moderate JavaScript skills. In my experience, it takes a larger and more experienced (expensive) team to do cross-platform successfully. 5/
So if you're a moderate-sized team of experienced iOS and Android developers who also know JavaScript reasonably well, and are comfortable debugging and bugfixing complex frameworks yourself, and have a strong desire to use one of these frameworks, they can add value. 6/
I know groups like that, and while they're reported success, they've all been "maybe?" on whether it's been worth it. Probably the biggest benefit they report is hot reloading (which is awesome!), but every one of them has said that it often doesn't actually work. So…YMMV. fin/
