I will fix and rebuild your ai generated or flutterflow app

Because most disputes come from projects that were never properly scoped. I review what you have and tell you honestly which package fits and what it will realistically take. It takes ten minutes and it protects both of us. Orders placed without this conversation may be cancelled.

Yes, that's the main thing I do. Send me the project or the repo. Sometimes the existing code is a solid starting point; sometimes a rebuild is faster and cheaper than patching it. I'll tell you which one you're looking at before you order, not after.

One screen is one view with its normal states: loading, empty, error, and the interactions on it. A settings page is one screen. A feed with filters, search, pagination and a detail view is three. When we scope your project I list the screens by name in our chat so there's no ambiguity later.

A revision is a round of changes to what was agreed in the scope: fixing a behaviour, adjusting a layout, correcting a bug in delivered work. Adding a screen, changing the data model, or adding a feature that wasn't in the scope isn't a revision. Those are custom offers, and I'm happy to quote them

Yes, and it has to be yours — $99/year for Apple, $25 one time for Google. The app must be published under your account so you own it. I handle the technical side of submission in the Premium package: builds, certificates, store listing setup, and fixing rejections.

It happens, and it's normal, often for privacy declarations or account deletion requirements rather than anything broken. In Premium, I handle rejection fixes for the work I delivered, at no extra cost. Note that each review round adds days to the timeline, which is why Premium is quoted at 30 days

I implement designs from Figma, screenshots, or a reference app you point me at. I don't design product UI from scratch. If you have nothing, I can build on a clean standard design system, but the result will look functional rather than distinctive. For real design work, hire a designer first.

Yes, on full delivery, with a README explaining setup and structure. It's written so another developer can take it over, that's the point of paying for a rebuild instead of another prototype.

Premium includes 30 days of support on delivered functionality. Beyond that, ongoing work is a separate arrangement. I prefer long-term clients, so this is usually easy to set up, but it isn't included inside a project package.

Not directly as a project, an undefined scope is the single most reliable way for both of us to end up unhappy. Start with the Code Audit package. You'll get a written assessment and a realistic plan, and if you go ahead with the rebuild afterwards, we'll already be working from the same document.