Omar Jadiani
← Back to posts

My Philosophy on Building Apps

Start with a lean MVP and a solid foundation, learn from real users, then grow on top once the direction is clear.

Most apps fail quietly, and the idea was often fine. People build too much before they know whether it mattered. I start with a small version, put the core in front of real users, change it from what I learn, and add more only after that. When the base is clear, each new feature is easier to add.

Start minimal

A first version should prove the idea. Save the rest of the feature list for later. I keep a base I can extend and the one workflow the MVP needs: a single path from start to finish, defaults that work, and boundaries that make the next layer obvious.

The code still has to be clean enough to extend. The scope should be narrow enough that you can explain the product in one sentence and ship it in days, before a first version stretches into months.

  • One core job, good enough to try today
  • Foundation patterns you will still want when you add more
  • Nice-to-haves left out when they only postpone what you learn

Test and learn

Until people use it, the code is a guess. In the first week I watch whether the right people use the app, come back, or show you what is missing. A perfect architecture can wait.

That usually means a small audience: a client pilot, a beta group, or one team inside a company. Watch what they do. Drop-off points, support threads, and the work they still do by hand tell you more than roadmap opinions. Change the product from what that evidence shows.

Build on a clear base

Once the base has held up with users, you choose what to add. Modules, polish, and integrations go on something that has already earned its place. Performance work, permissions, and deeper workflows come after the direction is clear.

This also avoids rebuilding features nobody wanted, or freezing a huge spec while the market moves.