# AI built app support [Read the public page](https://www.adarkcloud.com.au/services/vibe-coding-fixes) Review an app built with AI before relying on it for business. Identify access, data, hosting and maintenance gaps, then scope the next step. An AI built app review checks the code and environment behind a working demonstration. A repair or production release needs a defined scope, suitable expertise and evidence that important behaviour has been tested. Perth based, with remote support across Australia. From $79 an hour ex GST, with the fee agreed before work begins. Call Josh C on 0408 530 303. ## What we can help with - Code and hosting inventory - Access and data handling review - Fault reproduction and repair scope - Specialist development handover An app can look finished while its accounts, database and permissions remain unclear. Before it handles business records, someone needs to inspect the code and the services behind the screen. We can help establish the environment and review the support requirement. Repairs and specialist development are scoped after access and feasibility are known, with VibeZero an option for larger AI application work. ## Explain the behaviour as well as the visible screen A form submits without saving its record. One user can see another user’s data. A deployment works until its creator’s temporary account is removed. These examples need evidence from the code, hosting and data environment. Begin with the repository and service inventory. We agree on an appropriate private access method before secrets or customer records are shared. A screenshot can show a symptom but cannot establish how the application is built. ## Find the parts behind the demo Identify the repository, hosting, database, authentication and external services. Check who owns each account and whether the code can be recovered. A page that looks finished may still depend on temporary credentials or undocumented services. Do not put secrets or real customer records into a public support request. We agree on a suitable access method after the scope is established. ## Test the behaviour that matters Review permissions, validation and the actions the application takes. Normal use is only one case. Missing data, failed services and unauthorised users need deliberate checks. A repair should include evidence that the affected behaviour now works, along with any remaining limitations. Claims about universal security or production readiness need more than a successful demo. ## Agree on repair, replacement or handover The right result may be a small fix, a larger rebuild or a decision not to use the app. Custom development and specialist AI application work can be discussed with VibeZero. The business needs a clear owner for ongoing hosting, updates and support. ## Repair, rebuild or stop using the prototype A small correction may be feasible where the architecture and ownership are clear. A broader rebuild may be needed when the app’s basic access or data model is unsuitable. Sometimes the sensible decision is to keep it as a demonstration. The review should explain the evidence and limits behind that recommendation. An application intended for real users needs checks of unauthorised access, invalid input and failed services alongside its normal workflow. ## What the handover should include The agreed output can include an environment inventory, fault findings and a repair or development brief. Implemented work should have relevant acceptance evidence and documented limitations. The business needs ownership of the repository and services, plus a plan for updates, recovery and support. A specialist handover should make those responsibilities clear before a production release. ## Common questions ### Can you rescue every AI generated app? No. The code, data and access need to be reviewed first. We explain the feasible options after that review. ### Is a visual prototype ready for customer data? Not automatically. Authentication, permissions, storage and recovery need to be checked before live information is introduced. ### Do you need access to the source code? A meaningful code and behaviour review normally needs the repository and relevant environment details. We agree on the access and scope before investigating. ### Can we keep the current design? That depends on the review. A fault may be corrected without changing the visual design, while a larger rebuild may need a broader brief. ### Can the app go live straight after a repair? A repair addresses its agreed scope. A production release also needs appropriate access, data, recovery and operational checks, which must be discussed separately if they were not included. ## Useful next steps - [AI app review guide](https://www.adarkcloud.com.au/blog/5-things-ai-gets-wrong-when-building-your-app-vibe-coding) - [Application support](https://www.adarkcloud.com.au/services/application-support) Reviewed 2026-10-07 - [Ask for IT help](https://www.adarkcloud.com.au/contact) - [Check your IT basics](https://www.adarkcloud.com.au/tools/it-health-check)