Discussions

Man, your story hits close to home. I ran into something similar a while back with a small delivery app for local shops—started with cross-platform to keep things quick and cheap since the budget was tight and we needed both stores up fast. It worked okay at first, got us live without too much drama, but as orders ramped up the animations started feeling janky on older phones and some hardware features (like precise location in background) needed awkward workarounds that ate dev time anyway. Ended up regretting not going native for the core bits, though honestly for growing businesses I've seen the opposite too—folks who insist on separate native codebases from day one burn cash on parallel teams and miss market windows. These days I lean toward starting cross-platform for speed, then refactoring pain points later if needed. Check out https://phonedeck.net/mobile-software-development-service-for-growing-businesses/ sometime if you're weighing options; they seem to get that balance right without forcing one way or the other. Just my two cents from too many late nights debugging.