Skip to content
Siddharth Makadiya, product engineer — navy suit, glasses, looking at camera
SiddharthStill the person on the call.

About

Ten years in mobile — still the person on the call.

I am Siddharth Makadiya. I ship web and mobile products, and I help founders use AI without creating a second, worse codebase. Delivery often runs through Initio Tech Media when a project needs extra hands — you still talk to me.

  1. 01Read the letter
  2. 02Tap a decade
  3. 03Get a quote

10+years shipping mobile products people can install

4markets — US, UK, Canada, Australia — quoted in USD

LiveApp Store and Play listings you can open today

A letter, not a slogan

The job is a product someone can open.

I have spent 10+ years shipping mobile products — iOS, Android, Flutter, the boring store-listing work included. Consumer apps that had to survive review, ratings, and the second week after install. You can tap the live listings in the portfolio. That is the proof. I do not publish made-up quotes from founders at stealth startups.

Founders hire me when the gap is between a coder and a product engineer. I will write Dart and TypeScript. I will also pin the workflow, the data model, the auth boundary, and what “done” means before the first sprint burns a week of prompt-and-hope.

I work remotely from India with clients in the United States, United Kingdom, Canada, Australia. I do not pretend to be a US agency. I do overlap US and UK hours, quote in USD, and write like an adult.

AI is on the desk every day. Cursor, custom agents, and LLM APIs handle boilerplate so I can spend the hours on user experience, system architecture, and the business logic that actually has to be right. I review, test, and harden the result. A vibe-coded demo is useful. A customer cannot use it until auth, data, deploy, and failure paths exist.

If the brief is an agent, I want tools, permissions, a log, and a human fallback — not a chat widget bolted onto a form. If the brief is RAG, I want your private data connected with an explicit retrieval contract, not a magic box. If the brief is a weekend Cursor build, I will tell you what to keep and what to rebuild before you invite real users.

I take ownership of the path from concept to a store listing or a production URL. Stay on for a sprint of support, or I step back with a handover someone else can follow. Read the notes if you want to see how I think before we get on a call.

What I actually do

Three kinds of work. Pick the one that matches the product.

On the desk

Tools I ship with — not a keyword cloud.

Stack follows the product. Flutter when the job is one codebase and two stores. Next.js when the job is the web. Agents and RAG when the product has to act on private data, not just show it.

  • Mobile

    FlutterDartRiverpodiOSAndroid
  • Web

    Next.jsReactNode.jsNestJSTypeScript
  • Data

    PostgreSQLMongoDBFirebase
  • AI & ops

    CursorLLM APIsRAGn8nGitHub Actions

A decade in mobile, not a slogan

Tap a chapter. See what those years were actually for.

Store listings, crash reports, Flutter, now AI. Same habit: ship something people can open.

2023–now

Web, AI, and rescue

Same shipping habit, more surfaces: Next.js products, AI in the repo, agents that do a job, and vibe-coded apps that need a senior person before a customer sees them.

Ten years of mobile. The new work is making AI useful without creating a second, worse codebase.

Field school

Before a customer opens it, I check five things.

Tap what’s true on your product. Each tap teaches the lesson those ten years were actually for — then you get a plain read of where to start.

Mark all five. Then I’ll tell you where I’d start.

How we will actually work

  1. 01

    Scope the real job

    A short call or written brief. We pin down users, must-haves, budget band, and what “done” looks like. If it is not a fit, I will say so.

  2. 02

    Quote a clear path

    You get a written plan: milestones, stack, what I will ship, and what it costs in USD. No open-ended “we will see”.

  3. 03

    Build in the open

    Weekly progress you can click. Staging links, not slide decks. You always know what landed and what is next.

  4. 04

    Ship and hand over

    Production deploy, analytics, and a handover. Stay on for a sprint of support, or I step back cleanly.

Keep exploring

The site is a map, not a brochure

Next step

Want this to be about your product next?

Send the brief. I will tell you if a sprint is the right first page.