Building the Product

Should my MVP be a mobile app or a web app? My users are mostly on phones in smaller Indian cities.

A starting point

For a first MVP, a mobile-friendly web app almost always wins: no app-store review, no install friction, one codebase, and instant updates when you learn something. For users on cheaper Android phones and patchy networks (common when building outside the big startup hubs), a fast, light web page or a WhatsApp-first flow often beats asking them to install and keep a native app. Go native only when you genuinely need the camera, offline, push, or performance that the web can't give. This is a starting point, watch how your actual users behave and let that override the default.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 3 link-checked Read Use

Read

📄 Article
✓ Link checked Free Beginner

Why we picked it This is one of the few pieces that actually answers the question you asked, which is web app or native mobile app for the very first version, instead of a generic app-cost listicle. It gives you a plain decision framework: go native when the product lives in daily habits, alerts, or phone hardware, and go web when you need to remove friction and iterate fast. Read it as a starting point, then weigh it against what your own users in smaller cities will actually download and keep on a full phone.

Mobile App MVP vs. Web App MVP: How to Choose the Right First Step for Your Startup

From Asper Brothers by Mike Jackowski about 12 minute read

  • The platform choice is about user behaviour, not tech fashion: if the value is being in someone's pocket every day, lean mobile; if the value is fast learning and low-friction access, lean web.
  • Neither is automatically cheaper; scope and complexity drive cost far more than whether you picked web or native.
  • A responsive mobile-first web app is often the fastest way to validate demand before you commit to an app-store build and two codebases.
Open asperbrothers.com →
✍️ Essay
✓ Link checked Free Intermediate

Why we picked it This is Google's own guidance for exactly your users: budget Android phones, patchy networks, and expensive mobile data. It is the clearest single source on the design realities you will hit building outside the big startup hubs, from small app size to graceful behaviour when the connection drops. Use it as a checklist of constraints to design around, whichever way you go on web or native.

Build for Billions

From Android Developers by Google (Android Developers) multi-page guide

  • Design for intermittent and slow connectivity as the normal case: cache, degrade gracefully offline, and never assume a fast, always-on link.
  • Data cost is a real barrier, so keep app and page sizes small, prefer lighter image formats, and let people control how much data they spend.
  • Low-end devices have little RAM and weaker CPUs, so budget memory carefully and test on a genuinely cheap phone, not a flagship.
Open developer.android.com →

Use

🛠️ Tool
✓ Link checked India Freemium Beginner

Why we picked it If your users are on phones outside the big startup hubs, most of them already live inside WhatsApp and have never installed a startup's app. Before you spend months building an app or web product, you can run your whole first customer flow (orders, questions, reminders, a simple chatbot) through the WhatsApp Business Platform and learn what people actually want. Treat it as a way to validate the flow first, not as the final product.

WhatsApp Business Platform

From WhatsApp (Meta) by Meta product page plus API docs

  • It is Meta's official API for two-way business conversations, so you can automate replies, send templated updates, and route to a human without asking anyone to download anything.
  • Meta gives the first 1,000 service (customer-initiated) conversations per month free, so early validation costs almost nothing; business-initiated and higher volumes are priced per conversation.
  • The catch is you build on a channel you do not own, so use it to prove demand and shape the flow, then decide whether an app or web product is even needed.
Open whatsappbusiness.com →

People also ask

What actually counts as an MVP, and what's the smallest one I can get away with? An MVP is the least you can build (or fake) to test your single riskiest assumption, not a shrunken version of your dream product. Ask 'what's the ... Beginner 3 resources → How do I decide which features to cut from v1? Cut everything that doesn't help you learn whether people want the core thing. Pick the one workflow your earliest, most desperate customers need a... Beginner 3 resources → How long should building an MVP take? Weeks, not months. If your MVP will take more than 4-8 weeks, your scope is wrong, not your timeline. Airbnb, Stripe, and Twitch all launched narro... Beginner 3 resources → Should I build an MVP at all, or can I validate without one? If you haven't talked to ~20-30 potential customers yet, don't build anything, you're not validating, you're procrastinating in code. A concierge M... Beginner 3 resources → How do I get my first users for the MVP? Recruit them by hand, one conversation at a time, this is the whole point of an early startup. Go to where your users already are, DM them, email t... Beginner 2 resources → What's the difference between an MVP and just a cheap, half-finished product? An MVP is a learning tool with a clear hypothesis attached; a cheap product is just a bad product. The point isn't to spend less money, it's to buy... Intermediate 2 resources →