Google AI Studio Tutorial: Build a Car Restoration App (No Code)

By Beau Johnson··8 min read

Quick answer

I build Restore It Right, a car restoration app, in about 20 minutes with an idea from Idea Browser and Google AI Studio. I use three prompts (landing page, feature spec, PRD), a Google Omni hero video, and Firebase with Google Auth, and Gemini turns a photo of the car into a restoration roadmap.

In this video I build a working car restoration app called Restore It Right in about 20 minutes, without writing any code. I take a validated idea from Idea Browser, feed structured prompts into Google AI Studio, generate a hero video, connect Firebase for sign-in, and test the finished app on a 1969 Camaro. It's for anyone non-technical who wants to see what it actually takes to go from an idea to a working app.

What I cover in this video

  • 0:00 The finished landing page and how Idea Browser and Google AI Studio fit together
  • 4:32 The three prompts I rely on: landing page, PRD, and feature spec
  • 6:50 What I ask for in the landing page, plus design inspiration from 21st.dev and Dribbble
  • 12:10 Cutting the extra text and sections from the first draft
  • 12:55 Generating a rusted-to-restored Camaro video in Google Omni
  • 16:42 Overlaying the hero text on the video
  • 18:13 Wiring up Firebase, Google Auth, and photo upload
  • 21:18 Running my own action plan for a 1969 Camaro

Step 1: Start with a validated idea

I found this idea on Idea Browser, which has over 1,734 validated ideas drawn from search, Reddit, and Facebook demand. The problem it solves is simple. Someone buys an old Camaro and has the garage and the weekends to work on it, but six months later the car is under a tarp, untouched since week three. They stalled because they didn't know what to do next.

Restore It Right fixes that. You upload photos and answer a few questions, and you get a sequenced checklist of what to do today, what to order this week, and what to save for later. The idea page suggests starting with a $9.99 a month plan and a $29 a month tier for the full algorithm, and building the MVP around a simple intake form.

To keep things light, I didn't download every bit of research. I copied the idea context into Google AI Studio and dictated a short intro with Wispr Flow, a voice dictation tool I think is essential when you build with AI.

Step 2: The three prompts, with extra time on the landing page

Idea Browser has an Idea Builder with lots of prompts, but the three I use to get a project moving are the landing page, the feature spec, and the PRD (product requirements document). The landing page is where I spend extra time, because that's where AI output is weakest. Anyone can spin up a landing page now (my sister can, my dog can), so the extra effort is what helps you stand out.

After pasting in the landing page prompt, I added my own direction:

I want the landing page to be modern. I want it to be sleek. I want it to have less than 1,000 characters, and I want it to just convey what the app is about, what it does, who's it for, and the price. That's it. Don't overexplain things... I want the hero section to have a lot of motion using Framer Motion and modern architecture for the build-out. Be creative. Generate images if you have to.

For design inspiration, I show 21st.dev, where you can copy component code, and Dribbble, where you can grab splash screens or dashboard designs to use as reference images. In the end I didn't need them for this build, but sometimes you will.

The first draft still had too much text, so I asked AI Studio to simplify it, drop the success stories, remove the little pills above each section heading ("that is AI slop"), and cut down the hero copy. People don't read long pages anymore. Too many words and they'll leave.

Next I dropped in the feature spec. It covers user personas, the intake process, the AI task sequencing logic, the database schema, and the API endpoints, and AI Studio saved it to the root of the project. Then I added the PRD, which came back in 46 seconds. These can feel redundant, but they give the model direction. Without them it's guessing.

Step 3: A before-and-after hero video

Google Omni is basically Nano Banana for video. In Gemini I went to videos, picked Pro, and asked for a rusted, trashed '69 Camaro that turns into a fully restored one by the end of the clip. I downloaded the video, opened the code tab in AI Studio (you don't need to touch the code), and dragged the file into the source folder. Then I asked:

Can you please look for a video I dropped in the source folder? It's about a Camaro. I want that video to be in the hero section, and I want all the text overlaid... we need to make sure that the text is white, so it sticks out.

The result is a hero section that stops the scroll. That 10-second clip shows the whole restoration journey, which is exactly what this audience cares about.

Step 4: Backend, sign-in, and the roadmap

Next I asked AI Studio to connect everything. I wanted sign-up and sign-in, a dashboard, drag-and-drop photo upload, and an analysis with what to do, what parts to buy, and a restoration roadmap. I told it to use Firebase for authentication with Google Auth. Setting up the database isn't complicated: you enable Firebase Firestore and it's integrated into the backend for you.

This was the longest step, at 399 seconds. It built:

  • Firebase authentication with Google sign-in
  • A project intake and photo analysis wizard with drag-and-drop upload
  • Server-side AI generation through a dedicated backend API route using the Gemini 3.1 Pro preview model, so the API key is never exposed in the browser
  • A progress dashboard that shows tasks by phase with a circular progress gauge

To test it, I clicked share, set it to full screen and public, and opened the link in a new tab. I signed in with Google, described my 1969 Camaro (lots of rust, no motor, needs tires and shocks, and I want it as a daily driver), uploaded one photo, and generated the roadmap. It identified the missing engine and exhaust, the suspension and brakes, the rusty body panels, and the interior work, and then laid out the full roadmap.

If you're new to this, my Build an App with AI page covers more of the basics.

Key takeaways

  • Start from a validated idea so you know people actually want what you're building.
  • Three prompts get a project moving: landing page, feature spec, and PRD.
  • Spend your extra time on the landing page and keep it short: what it does, who it's for, and the price.
  • A Google Omni before-and-after video with white text on top makes a strong hero section.
  • Ask for Firebase with Google Auth, and keep your Gemini API key on a backend route so it isn't exposed in the browser.

FAQ

Can you build a full app in Google AI Studio without coding?

Yes. In this video I build a landing page, Google sign-in, a Firebase database, photo upload, and a Gemini-powered roadmap entirely by prompting Google AI Studio. I never touch the code.

Which prompts should I use first in Google AI Studio?

I use three: a landing page prompt, a feature spec prompt, and a PRD prompt. Together they give the model the direction it needs to build the app properly.

How do you add authentication and a database in Google AI Studio?

I asked it to set up Firebase for authentication with Google Auth, then enabled Firebase Firestore, which it integrated into the backend for me. That step took 399 seconds.

How do you keep the Gemini API key safe in a Google AI Studio app?

The build handles AI generation server-side through a dedicated backend API route, so the API key is never exposed in the browser.

Chapters

  1. 0:05The finished landing page
  2. 1:46The idea: daily tasks from the car's condition
  3. 2:06The tools, including Nano Banana
  4. 4:46The three prompts I rely on
  5. 5:13Why the landing page deserves extra time
  6. 6:21Sending the landing page prompt first
  7. 6:43What I ask for: modern and minimal
  8. 7:31A design site for splash screens and components
  9. 10:35Queuing the feature spec and the PRD
  10. 12:30Cutting the success stories and the extra sections
  11. 12:53Into Google Omni
  12. 13:18Prompting a rusted Camaro turning into a restored one
  13. 14:03Dropping in the feature spec
  14. 14:23The Camaro video comes back
  15. 14:47Dragging the video into the source folder
  16. 15:14The task sequencing engine, saved to root
  17. 15:4614 minutes to get the MVP 80% working
  18. 16:54Overlaying the hero text on the video
  19. 17:31The finished scroll-stopping page
  20. 18:28Wiring up sign-in and photo upload
  21. 18:41Firebase authentication with Google Auth
  22. 19:16The project intake and photo analysis wizard
  23. 19:31Keeping the Gemini key on a backend route
  24. 19:48The progress dashboard
  25. 21:02Running my own action plan
  26. 21:40A full roadmap for a 1969 Camaro

Transcript

Read the full transcript

0:00In this video, I'm going to show you how I build apps in 2026 by using two tools. This landing page we just built in under 20 minutes, and it is a car restoration app I found on the website Idea Browser. Idea Browser validates the idea, we plug it into Google AI Studio, and boom, comes out a beautiful working website that gives us an analysis that breaks down a roadmap for fixing up cars. Let's get right into it. I'm going to show you how easy it is to build apps in 2026. This is Idea Browser. This is where you go and find and validate startup ideas within minutes. So, maybe you have an idea yourself, you can run it through Idea Browser. Or maybe you just need some inspiration. You could go to the research section or the discover section

0:46to validate your idea or to find ideas that have already been validated using Google search, Reddit, Facebook. These are demand ideas of keywords that have already been scraped through the internet, and there's over 1,734 validated ideas, and we're going to be building out one of these ideas in this video with Google AI Studio. So, we're going to be building the landing page. We're going to be building the database, the backend, connecting so we could get users' emails. So, I'm going to get the idea going, and you're going to so I'm going to show you how simple it is to build ideas. All right, I really like this idea. Took just a few minutes. I've been into a lot of the restoration projects, not just with photos, but with

1:31cars, and we found one right here. It's actually a step-by-step process guide for car restoration projects. So, this is just like kind of what the app is about, and I'll show you how we build it in Google AI Studio. But, he says, um, "Restore it right breaks restoration projects into daily tasks based on the car condition and the goal. You basically upload your photos, answer a few questions, and you get a sequence checklist that tells you what to do today and what to order for the week and what to save for later. So, basically we're going to be using Google AI Studio and Nano Banana to be able to basically put this all together with in minutes. So, it says we can start at a $9.99 a month plan and then sell basic planning

2:17tools $29 a month for the full algorithm. So, build the MVP with a simple intake form. So, this is going to be pretty simple to build, but I'm going to show you how easy ideas can go from just text to actually come to life. So, here is just like the front page, you know, of the idea. It gives you a feasibility, opportunity, and problem and why now score, so you can kind of just get a good glimpse of the like, okay, this is this looks pretty easy to build. And you can also add in a business fit. If you do end up signing up for Idea Browser, you can actually create your own founders profile to see if you're going to be a match for this idea and it will give you an analysis whether you should do this idea or not. So, it talks about the lead magnet, the front end, and the core of like how we're going to be monetizing this and

3:02how we're going to be getting people with that free lead magnet. It talks about why now. With the growing popularity of do-it-yourself car restoration and the lack of digital tools tailored for phased guidance, now is the perfect time to launch a task sequencing tool that breaks down complex projects into manageable steps, reducing stalling, and improving user motivation. Proof signals. Car restorers often stall projects due to overwhelm, lack of clear direction, and accountability. With growing do-it-yourself trend but declining search volumes, this tool offers a unique market opportunity by addressing these needs with proprietary sequencing app. So, this will be a web app, very simple. And then we are the execution plan. It says launch a phased

3:47digital restoration guide for car enthusiasts offering a freemium platform with task sequencing. What I like about this is the marketing. You could partner up with car influencers on YouTube, Instagram, Reddit, TikTok, and be able to create some type of affiliate program. So, you don't need to be content creator to get this app out into the market. So, there's a lot there. I know that was a lot to cover, but I'm going to start with the basics on how I can actually take this idea and turn it into an actual landing page. How do we connect a database? And how do we get like behind the scenes called the back end connected so this actually works. There is a button right here. It's a blue button. Build this idea. There's two options. So, there's an AI workspace where you can kind of work inside idea

4:32browser and use your idea agent to kind of build this out. Or there is an idea builder that connects these prompts right to Google AI Studio. Very simple. There's a lot of prompts here on the left. I don't want to overwhelm you, but the most important ones that I like to use are the landing page, the PRD, and the feature specs. Those are the three main ones that are really good to get going. And I also like to spend a little bit more time on the landing page because that is where AI really isn't quite there yet. You do need a little bit of some design inspiration. Let's just say I'm not a designer, but to be able to give it a little bit more time on the landing page will really make the difference because anyone can now spin up a landing page, you know. My sister can. My dog can. I mean, literally

5:18anyone can spin up a landing page. So, we need to spend a little bit more time on the landing page so we stand out and not blend in. So, the first thing I like to do, and you could do this as well, if you don't want to, you know, spend too much time overloading the LLM of your choice, but you can download all of the data about this idea right now, but it's going to give you everything. I feel like that's sometimes a bit too much, especially if you're using, you know, this for the first time and you never built an app before. But, there is that option right here, download data, export all the research, analysis, the prompts, and everything. I'm just going to copy-paste this context basically of what the idea is to Google AI Studio. I'm going to be using Whisper Flow, so when you see me, I'm using a voice dictation software. I

6:03think it's 100% needed in today's age if you're building with AI. I found this app I really like, and I want to build it. It is a car restoration web app. I want to be able to help users restore their vehicles. Okay, so there we go, and then we're going to paste that in, and then we're going to first give it the landing page prompt. So, build this idea, idea builder, and there's a prompt here. It says popular. There's three of them. There's ad creatives, brand package, and landing page. This is the one that is active. You could just copy, or you could just go click on Google AI Studio, and it'll pull up Google AI Studio with that prompt copied out already. Then, we're going to go back, paste that in. That is the prompt for the landing page. I want the landing page to be modern. I want it to be sleek. I want it to have less than 1,000

6:50characters, and I want it to just convey what the app is about, what it does, who's it for, and the price. That's it. Don't overexplain things. Don't put too much text on the screen. I want the hero section to have a lot of motion using Framer Motion and modern architecture for the build-out. Be creative. Generate images if you have to. Okay, there we go. And, you know, I just want to show you this is a huge piece of the puzzle that I've been using to build out my websites. There's a lot of free asset websites out there. You know, you can use 21st.dev, you could use Dribbble, you could use So, here's Dribbble. This is a just a great way This is like a website for designers, and it's just a great way to get some splash screens going for your web mobile app, or maybe

7:35you are trying to design a dashboard, and you just really don't know how to do it. Come in here, and you can copy any of these designs to use as a reference photo. So, 21st.dev is a great place to be able to just also get inspiration. What I like here is you can copy the code, which I really like. So, we'll circle back to this and I'll just show you kind of what Google AI Studio comes up with and how we can just make a few tweaks with just like adding a different type of hero section. So, we'll let that load in the background. We'll close I think one of the best parts about just building in 2026 is that is how fast you could see your idea come to life. Like this time last year, it was not possible. And if it was, the landing

8:21pages were terrible. There would be so many bugs that the app would be totally unusable. Today, you could actually, with no experience, no technical background, come to Idea Browser. You have a really good idea, run it through Idea Browser, make sure it's validated, make sure people want it, and actually get structured prompts to be able to feed into Google AI Studio to see the idea come to life. There is something about seeing something or taking something from the unseen that's not tangible and making it actually tangible. Just that in itself should give you motivation and it should give you confidence to be able to build these ideas. Don't be scared. Don't feel like, "Oh, no, I don't know what to do." You got this. This is why we're making the

9:06videos just to show people that you could build in this day and age. So, here's kind of what it came up with, the design previews, which I really like. You could choose different type of typography and coloring of kind of what you're going for. I actually like the first one. And we might not just stick with that one, but I'm going to go with the first one because, like I said, 21st.dev has beautiful designs. These are actual designers building in here. Like I'll show you this, for example. Just it's beautiful. It's beautiful and and sometimes you got to tweak the the LLM a little bit more just to get what you're looking for. I really like this design, too. I don't know how you can implement that somehow, but there's so many so many in here. This is just for

9:51the hero section. Let's see. It just looks good. It just looks good. We'll play around with it and just see what it comes up with. This one's kind of cool. Oh, and you can kind of play with the cards. I like that. Okay, so let's see what it came up with. It's still going. It's been going for about a minute now. I've I've successfully designed and built the landing page for Restore It Right. The single page application is structured to convert using a high-contrast dark theme, immersive hero section, it implemented it implemented a responsive hero section, and trust indicators, clear value proposition. The copy is punching direct clarifying that the app breaks down complex restoration projects into bite-size tasks. So, the next step is kind of queuing up the um, the feature spec and the PRD prompt. So,

10:38I think I'll go to the feature spec prompt. And just to give you an idea of how robust this prompt is, it's pretty insane. It's just Think of these prompts as like the building blocks, the foundation to your web app or mobile app. You can tweak them, you can go through them, you can run them through Google AI Studio and make sure that, "Hey, is this is in alignment with my actual project?" This is just the glue that kind of holds it all together. Can you build without these prompts? Yes, but it's nice to just have these ready for people that are just getting started. So, just the first sentence is generate comprehensive feature specifications that provide clear direction for development teams. This should include detailed user stories, acceptance criteria, technical requirements, and implementation guidelines. Just goes through the entire feature spec of like who's it for, why

11:25is it being built, who are we going to be targeting as far as businesses or just do-it-yourselfers, things like that. And this is important context to give to the LLM that's building your app. Without it, it has no direction. So, we're going to let it finish and do its thing, and then we could get into actually seeing this thing come to life. Wow, this actually looks really good. Don't let your dream car rust in peace. The AI-powered guide that breaks down your restoration project into simple daily tasks. Know exactly what to do today, what what to order tomorrow, and finish the build. I love that. You don't want too many words on your landing page. Trust me, this is the attention economy, and when you when you This is too many words. Honestly, it's too much.

12:10People don't want to read through anything anymore. And if there's too many words, they're going to get overwhelmed, they're going to click off your landing page and go somewhere else. There's too much here, too much here, too much here, and then too much there. It's just it's too much, so we'll simplify that. There is just way too much text on this landing page. Simplify it. We don't need success stories. We don't need the method. Well, maybe keep the method, but we don't need from overwhelmed to actual. Remove the little pills in the header or H1 of each section. That is AI slop. I don't like it. And simplify the hero section to be less wordy. All right, so that's going to be cooking in the background. I thought we'd go into Google Omni. If you

12:55haven't heard of Google Omni, it's basically the Nano Banana for video. You can create some really nice hero section videos that you can overlay your text all on top. So, I've been using it more and more lately. So, we're going to just go into Google Gemini and then click videos. And then I just stick with Pro, so it understands the full context. And here's what I'm going to do. I want a rusted old '69 Camaro that has been completely trashed turned into a beautiful restored '69 Camaro. So, the start of the video is the car completely destroyed, and the end of the video, it is completely restored, beautiful. That is what we're going to um have the text overlay. You can go

13:40back into here, see if there's anything that Nothing that has been sticking out. Not only do they have, you know, good hero sections, you could just get different components for your landing page, for your dashboard, for a modal that pops up, for a floating dock, anything. Those little things do make the difference, in my opinion. I'll be dropping in the feature spec. So, it's still working on my previous prompt, but I'm going to drop in that feature spec now. Here is the feature spec. Take a look at it. This is the prompt for the feature spec to build it out, to make sure the app actually works. Okay, so it's came back here, and I simplified the landing page according to the instructions, and just made it more simple, which I love. You want it to be simple, and then I love it. Looks great. So, let's go back to the camera or Camaro. Camaro restoration video. We got

14:26it, baby. And I mean, honestly, I think '69 Camaro, 1969 Camaro, is the greatest old-school vehicle of our Okay, so, we're going to download that video. I'm going to go into this code section here. Don't be intimidated when you open it. This is just the code base. You don't need to touch it. We're just going to take that downloaded video, and I'm going to drag it into the source folder, and that's it. And then go back to preview. We can We can be done with that. Okay, so, I'm going to We'll circle back to that later. We're going to hit it with this feature spec, and we're going to let it cook. Don't skip this part. Dad, came back. I have generated the comprehensive feature specifications document based on the Restore It Right business context and your provided template. The document, which details

15:11the AI-powered project intake and task sequencing engine, saved to the root directory. It covers user personas and stories, focusing on the overwhelmed hobbyist, functional requirements, outlining the intake process and the AI-driven task sequencing logic, and then non-technical and functional specs detailing the database schema and project task API endpoints and performance expectations. So, just figuring out how the back end looks to actually make this web app work. And then a 14-day phased approach for MVP and deployment. That is not the case anymore. It will take 14 minutes to get the MVP at least 80% working. So, and then success metrics, like how it judges success, is tracking intake completion, time to first action, and beta user

15:57retention. So, very cool. I'm also going to drop in the PRD cuz this is super helpful. Also, like the vision and road map for your product, very important. Don't skip this either. Basically, just says you are a senior product manager and technical specification expert, create a comprehensive PRD, product requirements document, that clearly defines what to build, why to build it, and how success will be measured. So, I know it seems redundant, but this is a huge one that you need to put in there. Here is my product requirements document. Here is the prompt. Please fill it out and then store it in the code base and apply whatever is necessary. So, it came back within seconds, uh 46 seconds. I have successfully completed the PRD and serving it as a comprehensive blueprint for the platform. Comes up with

16:42strategic alignment, user and functional requirements, technical and UI specifications, and execution strategy. Very good. So, before we drift too much further, I want to take that video that we generated in Google Omni and have the text overlaid in front of it. Can you please look for a video I dropped in the source folder? It's about a Camaro. I want that video to be in the hero section, and I want all the text overlaid. So, if we're able to showcase that somehow, where it's the text overlaid on top of the hero video, we need to make sure that the text is white, so it sticks out. And then the current project little hero card can be the next section of the landing page. I am the super impressed. Like look at

17:28this. Doesn't this just look beautiful? Within just 20 minutes, we have a scroll stopping hero section. Restore it right. I think this looks amazing. Shout out to 69 Camaro. But look, I mean, literally just walking you through the hero journey or through the user's journey of like, "Okay, I have an older vehicle. I want to restore it." You could see it in this just 10-second video of like the process, the journey. And that should resonate with people that are interested in restoring vehicles. So, that's huge. It did a great job at moving this card down below. And then did a great job of just keeping text minimal. So, this is great. I'm happy with this. I want to now start connecting the database, the back end, and to actually get the

18:13functionality working. So, after we did the PRD, the features back, and the landing page prompt, we're now ready to actually connect everything. Can you actually verify and connect everything on the back end so this works? I want to be able to sign up, sign into the dashboard, and I want to be able to drag and drop a photo of an old car, and have it come back with an analysis of what to do, what parts to buy, and a road map for the restoration. So, I think we need to set up Firebase for authentication. We should use Google Auth to be able to authenticate users. And I want to be able to build this out completely. There you go. So, when setting up your database, it's not super complicated. It's simple. You just enable Firebase Firestore, and it automatically

18:59integrates it into your back end. Super simple. Okay, so that was the longest process in this whole build. It took 399 seconds. And it was just basically connecting the back end database so we can actually get users. So, Firebase with Google OAuth, project intake and photo analysis wizard. It built an intake form allowing users to describe their car, utilize the drag-and-drop file upload to submit photos of their current build directly from the browser, and then it has server-side AI generation. It handled securely via a dedicated API back-end route utilizing the Gemini 3.1 Pro preview model, and AI processes the structured vehicle profile file, raw imagery, and sequence a step-by-step restoration checklist

19:44strictly ensuring API keys are never exposed. Very important. So, digital progress dashboard. It implemented a responsive workspace to visualize tasks by by phase integrated with a circular progress gauge. I love that. It hardened the database security, and the application is deployed full stack, and I can access your API key in the settings secret panel. Your environment is live and ready to begin. Let's go. So, if you want to actually see how your site looks, um there's just a quick little share button here, and I go default to full screen, and then I go to public, and then that way we could just copy the link and actually pull it up in a different tab just to see kind of how it fills it out, how it looks. But, I am fired up, man. Building apps this time

20:31of year has become so much easier compared to last year. This was not possible at all. Look at this. Nice, clean, beautiful what the app does, who it's for, and how much it costs. Don't overthink it. So, that is beautiful. That is great, and I know we didn't use any assets from 21st.dev, but I just don't think it's needed. It did a really good job. Sometimes you will need it, sometimes you won't. It just depends on how well the LLM does, and how your vision is for the project. So, get my action plan. It's going to pull up my Google account, and let's see. For logging in and signing up, all right, here we are in the dashboard. Really simple, no projects yet. Upload a photo of your project car and let our AI build a step-by-step restoration roadmap. It's

21:18a 1969 Camaro. There is a ton of rust. It's missing the motor. It needs new tires. It's missing shocks, and it's in really rough condition. I want it to be my daily driver. Okay. Uploaded one photo and generate restoration roadmap. Analyzing project. Wow, completely blown away. It came up with this roadmap of my piece of junk Camaro here. Gave a no engine, no exhaust, H suspension and brakes, rusty body panels, interior needs restoration, and it came up with a nice beautiful roadmap. That's what it looks like building AI apps in this day and age to go from idea browser, basically just browsing ideas for a car restoration project, putting a few

22:04prompts into Google AI Studio, and coming up with a beautiful roadmap to actually fix the vehicles that you're wanting to work on. I love it. So, I'll put the links to those two apps down below, Google AI Studio, as well as Idea Browser. Check them out. I mean, come on, you got 20-30 minutes to spare to actually build your idea out. We'll see you in the next one. Have a blessed day.

Ready to start building with AI?

Join Shipping Skool free — 4 live build sessions a week, courses, and a community that ships.

Join Shipping Skool

Keep reading