Services

Vibe coded app? I'll take it to production

You built your app with Lovable, Bolt, Cursor or after a course, the demo works, and now you're stuck. I've been a full stack developer since 2010 and I've published eight apps of my own on the stores: the things you're stuck on are my everyday work.

Let's talk for 15 minutes

  • 16 years of development
  • 8 apps published
  • almost 11 years at Crisalix
  • mentor at Nana Bianca

Where almost everyone gets stuck

  • Real login and accounts: password reset, account deletion, sessions that stay up.
  • Payments: Stripe on the web and, on the stores, the in-app purchases Apple and Google require for digital content.
  • User data: a database without access rules lets anyone read everything. In 2025 it happened to more than 170 apps built with Lovable.
  • Domain, deploy and emails that actually arrive, and not in spam.
  • Apple and Google review, which rejects apps that do too little, apps without account deletion and apps that take payments outside the store.
  • Costs that grow with users, especially calls to AI models.
  • Backups and alerts when something breaks: the demo has none.
  • Code nobody can change anymore, not even the AI that wrote it.

How I work: two steps

We start from the code you have. I don't rewrite from scratch unless it's needed, and if it is, I tell you why.

  1. The review

    I go through the code and the app, and give you in writing what is missing to go live, ordered by risk: first what could lose you data or money, then the rest. It is a job of its own, and the document stays yours even if you continue with someone else.

  2. Going to production

    Based on the review I give you a fixed price, before starting. I take the app live, on the web or on the stores, and the code is yours from day one.

October 2026: three apps, free review

I'm choosing three apps built with AI, and for each one the review is free. In return I ask for permission to tell the story with the app's name, access to the code and a date by which you want to be live. To apply, write to me with the form below.

Where I've done it

Lumideo

My latest app, on the App Store and Google Play: login, in-app subscriptions with StoreKit 2 and Play Billing, notifications, cloud functions, and Apple and Google reviews passed.

Ruralis

When I joined there was little more than a draft. I built the foundations of the platform: the serverless backend on AWS, the owners app on the stores, payments with Stripe.

What I work with

I read the code that comes out of Lovable, Bolt, Cursor, Replit and v0. I work with React Native and Expo, Node.js and TypeScript, Firebase, AWS and Stripe, and I have been publishing apps on the stores since 2010.

Do you have an AI-built app you can't get live?

Send me the link or tell me where you are. In the first call we find out what is missing and whether it makes sense to work together.

Let's talk for 15 minutes

Contact

Let's talk

Tell me what you want to build. I'll reply within 24-48 hours.

Rather pick the time yourself?

Book 15 minutes

The questions you're asking yourself

  • I reply within the hour. When I start a project, I see it through. Whether I'm in Naples, Mexico or Japan, I work on European hours: within my working day, I reply within the hour. You know this before we start, not after.
  • It's yours from day one. The code on GitHub, server access, every project document: shared with you from minute zero. Not on delivery — right away. Which means the work carries on without me.
  • The price doesn't move. Once agreed, the price stays. Even if I got the hours wrong: my mistake, my cost. It changes only if what needs building changes, and in that case you hear it from me first — not on the invoice.
  • You're buying a date, not a file. A delivery date and something running in production. Not a file, not a zip: on the day I told you, it's live and you're using it. And from then on it's yours, because you've had it since day one.