Web App Development

A website is most of the time just a visual representation of your work. It is static and is used for reading it's content while a web app is well used. A web app consists of authentication, roles & permissions, real data that goes somewhere and is displayed in a meaningful way.

Whichever fits the problem. Most of the time I would suggest React or Next.js since it has become the gold standard in single-page applications. If you prefer something other than React, Svelte can be a stellar alternative. Astro is content-first with islands of interactivity. There are a lot of different frameworks and options, which I will go through with you, explaining their pros and cons.

That is part of the build rather than a separate project. Supabase or Firebase for authentication, storage and data, or a custom Node.js backend with MongoDB or Postgres when the project deserves one. Either way the schema is documented, so it can be maintained easily.

Performance budgets are set before we build and the numbers are checked as we go: bundle size, response times, how much JavaScript a first-time visitor downloads. Features get added against those budgets, so a year in the product is still quick rather than a study in why it got slow.

Yes, unit tests are covered as the minimum. Integration tests can also be done so that you know that your app is sturdy and it will not break on the slightest inconvinience..

Yes, and I start with an honest assessment of what is already there. Sometimes the fastest route is keeping what works and rebuilding the rest. Sometimes it is starting again. I will tell you which I think it is and why, before you have paid for a rewrite you did not need.