Web apps and PWAs
A website stops being enough once you need user accounts, an admin panel and data that changes in real time. That is where a web application starts. I build them as PWAs, so they run in the browser and install on a phone like any other app.
Tell me about your ideaFirst working version: 6–10 weeks. We set the scope in a workshop before the quote, so the deadline is realistic rather than aspirational.
A PWA runs in the browser and the user adds it to their home screen in one tap. It never goes through App Store or Google Play review, you pay no commission on sales, and you do not wait days for every fix to be approved. An update reaches everyone the moment it ships. One codebase covers Android, iPhone and desktop instead of three separate projects.
A PWA is out when the app needs deep system access: continuously reading sensors in the background, Bluetooth on iPhone, or being sold through an app store. If that is your case I will say so on the first call rather than build something that later has to be rewritten. For the large majority of business use cases a PWA is cheaper and faster to ship.
We start with the smallest version that makes sense, usually one complete end-to-end flow. I would rather you held a working thing after six weeks and could show it to someone than wait half a year for a full feature set where half turns out to be unnecessary.
Personal project
Analytics cookies
I use Google Analytics to see which content is useful. No tracking scripts run without your consent. Essential cookies always work, because the site will not function without them. Details in the privacy policy