Question 1

How fast will my website actually be?

Accepted Answer

Every site I ship targets a sub-2-second first load on a normal 4G connection and green Core Web Vitals. That comes from server-rendered pages, compressed and correctly sized images, lazy loading below the fold, minimal third-party scripts and CDN delivery. I test the build on throttled mobile before launch, not after.

Question 2

How long does a website or app take to build?

Accepted Answer

A focused marketing or portfolio site is typically 1–2 weeks. A booking, ecommerce or management system is usually 3–6 weeks. A SaaS MVP with accounts, payments and a dashboard is normally 6–10 weeks. You get a written scope with milestone dates up front, and I ship a working preview link from week one so you can follow progress instead of waiting for a reveal.

Question 3

Can you work from my existing brand or designs?

Accepted Answer

Yes. I can build from your Figma files, brand guidelines or an existing site, or create the design direction myself if you don't have one. Either way you approve the visual direction before full build starts.

Question 4

What is a PWA, and should I choose one over a native app?

Accepted Answer

A Progressive Web App is a web app that installs to the home screen, opens full screen without a browser bar, works offline for cached content and can send push notifications. It's the right choice for most businesses: one codebase for iOS, Android and desktop, instant updates, no app store review and no store fees. Choose native when you need deep hardware or platform features — background location tracking, Bluetooth peripherals, HealthKit, or store-billed in-app purchases.

Question 5

Do you build native mobile apps too?

Accepted Answer

Yes. I build installable PWAs first, then wrap and extend them for the App Store and Google Play when you need native capabilities or a store presence. That keeps one codebase driving web, Android and iOS, so you're not paying to build and maintain the same product three times.

Question 6

Will my app work offline and on older phones?

Accepted Answer

PWAs I build cache their shell and key data so users can keep browsing and queue actions without signal, syncing once they reconnect. Everything is tested on mid-range Android and older iPhones, not just a flagship device.

Question 7

Can you build internal tools and dashboards for my team?

Accepted Answer

That's a large part of my work — order intake, repair tracking, laundry and cleaning operations, school administration, nursery daily logs and hotel booking are all systems I've shipped and run in production. They come with role-based access, audit-friendly records and exports.

Question 8

How do you keep my website and data secure?

Accepted Answer

HTTPS everywhere, hardened security headers, and no secrets in the browser bundle. Data sits behind row-level security policies so one account can never read another's records, roles are validated on the server rather than in the client, all input is validated before it reaches the database, and dependencies are scanned and patched. Payments and authentication run through vetted providers such as Stripe and Supabase — I never store raw card details or plaintext passwords.

Question 9

Who owns the code and the accounts?

Accepted Answer

You do. The repository, domain, hosting and third-party accounts are in your name, handed over at launch with documentation. There's no lock-in and no hostage hosting — you can take the project to another developer at any point.

Question 10

What happens if something breaks after launch?

Accepted Answer

Every build ships with error monitoring and automated backups. Critical issues — a site down, checkout or login broken — get a same-day response. I keep a short list of clients so support isn't queued behind a ticket system.

Question 11

Do you offer ongoing support after the project is delivered?

Accepted Answer

Yes. Every project includes 30 days of post-launch support for fixes and small adjustments at no extra cost. After that you can move onto a monthly care plan covering dependency and security updates, uptime monitoring, backups, performance checks, content changes and a block of hours for new features.

Question 12

Can you improve or take over a site someone else built?

Accepted Answer

Often, yes. I start with a short audit of the codebase, hosting and performance, then give you an honest recommendation on whether to improve what exists or rebuild. If a rebuild isn't worth your money, I'll say so.

Question 13

How much does a project cost, and how do payments work?

Accepted Answer

Pricing is fixed per project once scope is agreed, so there are no hourly surprises. Cost depends on how much of the product needs building — a marketing site sits at the low end, a multi-role SaaS platform at the high end. Standard terms are a deposit to start, a milestone payment mid-build and the balance at launch. Send me your requirements and you'll get a written quote.

Question 14

Which countries do you work with?

Accepted Answer

I work remotely with founders and businesses in Ireland, Switzerland, England and Nigeria, and have shipped production builds for clients in Ethiopia and Cyprus. Calls are scheduled around your timezone.

Question 15

Do you also teach people to build apps themselves?

Accepted Answer

Yes. I run 1:1 and small-group app-building training covering modern web and PWA development, AI-assisted building and shipping to production. It suits founders who want to prototype their own ideas and teams who want to maintain what I build for them.

Questions worth asking before you build.

Websites & performance