Skip to article
← Back to the notebook
Guides / 02

Website or app? Start with the use case, not the technology.

The right first release does not always belong in an app store. Choose what to build without adding unnecessary work.

In this article

If people need to discover you, start with a website

When the goal is to explain services, show work or receive enquiries, a website is often a reasonable starting point. People can open a shared link without installing anything.

An owned website can work alongside Instagram, not replace it. Social posts can lead to a clear offer, examples and contact options. Search visibility still needs work; having a website does not guarantee rankings.

A website can also be a working tool

Internal dashboards, calculators and platforms with user accounts can run in a browser. Not every business tool needs an app-store release.

For teams working across computers with shared data, consider a web application first. Then evaluate offline use, notifications and device features.

An app makes sense when people return

A mobile app can fit a frequently used product that depends on phone capabilities. A camera, NFC or specific background processes can justify native development.

Apps also require device testing, store submissions, policy compliance and ongoing maintenance. A home-screen icon alone is not a reason to take on that work. Available capabilities depend on the operating system and its permissions.

Do not treat Android and iOS as an automatic bundle

Ask which devices your users actually have. Native Android, cross-platform development and web each involve different trade-offs in integration, maintenance and user experience.

At Luby, scope comes before technology. We use Kotlin for native Android, Flutter when it fits and an external partner for native iOS. A project does not automatically need all three.

Five questions for a first release

Bring these answers to the first conversation. If you do not know one yet, record it as an assumption to validate.

  • What specific task should the person complete?
  • Will they do it once or return every week?
  • Does it need camera, NFC, location or another device capability?
  • Does it need to work offline?
  • Who will maintain the product after launch?

Build a version you can maintain

Start with the most important journey and test whether it meets the need. A focused scope leaves room to review decisions before adding features.

Websites and apps can complement each other. You do not need to build both on day one.

Let’s bring it back to your project.

Tell us what you need to build