Should I build an APP or WEB? (as a web developer entrepreneur)
You(Web dev entrepreneur): Hey Kyle, I'm building an MVP and I'm unsure whether to go with web, app, or both. Any thoughts?
Kyle: Okay, I got it. Then let's see if we should make an app today or not. First, what I'm curious about is what you're building, because as always, the glorified answer should be: it depends. Some services absolutely need an app, while others work perfectly fine without one. But here's my general advice: unless you absolutely need an app, stick to web. (If you do need an app, we can discuss that later - for now, trust your intuition.)
You(Web dev entrepreneur): But.... can't we just do both? With cross-platform frameworks like React Native and Flutter, plus Expo's web support... wouldn't it be straightforward?
Kyle: Well, yes but no. Just start with web. Let me explain why apps can be a resource-draining challenge with unexpected complications:
- Steeper Learning Curve
The learning curve of building an app as a web dev is more demanding than you might expect. Yes, frameworks like React Native and Flutter make app development more accessible to web developers. However, the underlying architecture is quite different. While adding features might be straightforward, debugging can be a nightmare unless you understand app fundamentals. Many cross-platform library issues require native-level knowledge to resolve. When you're focusing on growing your business, this extra complexity isn't ideal.
- Higher Initial User Acquisition Cost
User acquisition costs (CAC) are typically higher for apps. Think about the user journey: for a website, users can simply click a link from Google and start exploring. For an app, they need to visit your site or app store, download the app, install it, then log in - that's a lot more friction. Unless you're heavily investing in app store optimization (ASO) or paid advertising, getting those initial users is more challenging than with web.
- Maintenance Overhead
This is perhaps the biggest argument against starting with an app - you're essentially maintaining multiple codebases (web, iOS, Android). In the early startup phase, you need to move fast: testing features, gathering user feedback, and iterating quickly. Having to implement and test changes across multiple platforms can significantly slow down this crucial process. In order to do that, drop the app for now, and just focus on figuring out what users want.
In summary, unless your service absolutely requires an app, start with web-only and add app later. However, always evaluate your specific context.
Consider factors like:
- User expectations in your industry
- You and your team's mobile development expertise
- Industry-specific requirements
- Available resources
You(Web dev entrepreneur): But Kyle, what if you absolutely need an app? Are any ways to build one efficiently with minimal resources?
Kyle: Of course there are. Let's save that discussion for next time.