Build a Pet-Sitting Booking App with Google AI Studio and Claude
Apps it uses
A friend who had just started a pet-sitting and dog-walking business asked me to build a booking app.
I used Google AI Studio to design the initial prototype. The process was straightforward, and I had a basic working system running within two hours. AI Studio created a Firebase database to store the details and was also effective at designing frontend changes. It published the app for me, and the resulting UI was intuitive.
After demonstrating the app, I identified many additional features that needed to be added. This went beyond AI Studio’s capabilities, so I exported the code from AI Studio and started using Claude. I asked Claude to analyze the code and suggest the required changes.
Claude identified critical security flaws in the database. I fixed them manually at first, but then realized that Claude could access the Firebase database and fix issues automatically. I continued prompting Claude with additional feature requests, and it built them. There were errors along the way, so I needed to be familiar with Google Chrome’s developer tools to copy the errors and ask Claude how to fix them.
I used MailJS for email templates and Resend for email transport. I stored the app in GitHub and allowed Claude to access the repository so it could commit changes automatically. I ran the app locally with npm during development and then hosted it on Vercel. Eventually, I purchased an inexpensive domain name, and the app is currently hosted at Names.
One major problem was that when Google AI Studio created the Firebase database, the permissions were locked, preventing me from making administrative changes. I solved this by recreating the database and asking Claude to write the SQL query to set it up. The permissions were still tricky, and I had to continue asking Claude to correct them.
Google’s service permissions can be difficult to understand, and finding the correct settings was not always easy. Firebase was also complex to navigate, and getting the permissions configured correctly took time.
Once I allowed Claude to connect to the app and its background services through the Google plugin, development became much faster. However, you need to trust the tool carefully and always work on a copy of the live app.
Overall, I think app development with Google AI Studio and Claude is impressive. You can create professional apps quickly. I come from an IT support background, though, and I think people who are new to IT may find it difficult to troubleshoot errors without a basic understanding of networking and systems administration.
I also built a litter-tracking app using ChatGPT, and it was equally effective. I eventually started using Codex and Claude Code, but I think standard Claude and ChatGPT are more intuitive for nontechnical users.
Step-by-step
- I used Google AI Studio to create an initial booking-app prototype for a pet-sitting and dog-walking business.
- I used the Firebase database created by AI Studio to store the app’s details and used AI Studio to design frontend changes.
- I published the initial app with AI Studio and demonstrated it to identify additional features.
- I exported the code from AI Studio and asked Claude to analyze it and suggest changes.
- I addressed the critical database security flaws identified by Claude, first manually and later by allowing Claude to access the Firebase database.
- I prompted Claude to build additional features and used Google Chrome’s developer tools to copy errors and ask Claude for fixes.
- I recreated the Firebase database when AI Studio’s locked permissions prevented administrative changes, then asked Claude to write the SQL query to set it up.
- I used MailJS for email templates and Resend for email transport.
- I stored the app in GitHub and allowed Claude to commit changes automatically.
- I ran the app locally with npm during development, hosted it on Vercel, and later purchased an inexpensive domain name that is currently hosted at Names.
- I connected Claude to the app and background services through the Google plugin, while continuing to work on a copy of the live app.
- Industries
- Professional ServicesSoftware & Technology
5 comments
Have a question about this workflow, or a way to improve it?
Log in to comment Create a free accountI can't help you with Firebase permissions, so let me be useful from the other side: I'm your friend's customer. Two dogs, about three hours of walking a day, and I've paid people to take them out. What made me switch sitters wasn't a booking flow. It was one photo, sent halfway through the walk. Nothing else changed, and I stopped thinking about it. An owner handing over their dog isn't buying an hour of walking, they're buying an hour of not worrying, and the booking is just the paperwork around that. If the app only owns the paperwork, the part that earns the repeat business still lives in WhatsApp. Which is really my question, and it comes from my own scar tissue rather than any judgement of the build. Does your friend use it? I've built tools for other people that quietly died because the new thing asked for more discipline than the old messy way, and the old messy way was already good enough at the bit the customer actually cared about. If she's still sending the photos by hand, that's not a gap in the app, that's the app pointing at where it should have started.
This is a great build!
Super detailed, thanks for sharing!
i want to know more about the litter tracking app
this is a great example of where AI app building gets genuinely useful, fast prototyping first, then using Claude to handle the harder backend and security work. The Firebase permission issues are also a good reminder that AI can speed up development a lot, but understanding the underlying system still matters.
Posting guidelines