You’re not wrong. Depends on how much time the developer wants to spend to make it work, what their tolerance is for quality and testing thoroughly, etc. If using a multiplatform framework can get it 70% of the way there, some may be motivated to put in that extra 30% (I’m making numbers up). I don’t want it to be a single-dev effort forever, though. I do eventually want more developers working on it.
Discussion
Well it depends how much is there to "make things work". 70% of a kind 1 feed is a day-long project. 70% of multiplatform picture-in-picture background video playback controlled by AppleTV/Chromecast at the same time as the AppleWatch and GalaxyWatch with in-device controls to like, zap and report is a multi-month clusterfuck of work.
The key is the size of the app. To me Olas is already too big to be maintainable by a single dev in two platforms.
That’s fair. Alternatives could be to:
1. Continue building native for one platform and focus on speed and quality. Make the product desirable enough that there will be demand for other platforms, and desire from other developers to contribute to (or hire developers to build on) those other platforms.
2. Same as 1 but use a multiplatform framework, which reduces the amount of code that needs to be rewritten.
On 2, the true question is: can you make that product desirable enough faster than on 1? It's all about user adoption.