How to Build a Landing Page with Stitch and Google AI Studio
Prefer to watch? Watch on YouTube · Subscribe for new builds · Read the transcript
In this build-along I try to get from a raw idea to a working landing page and the start of a real MVP as fast as I can, using as few prompts as possible. I use Idea Browser for the idea and its product requirements document, Stitch 2.0 for the design, and Google AI Studio to build the app and connect a Firebase backend. It's for non-technical people who want to get an idea live without writing code.
I recorded this in June 2026. These tools change fast, so check the current docs if something looks different when you try it.
What I cover in this video
- 0:00: The goal: go from zero to one with Idea Browser and Google AI Studio, and count how many prompts it takes.
- 0:45: Pulling the product requirements document (PRD) out of the Idea Browser build kit.
- 1:30: The landing page and dashboard I generated in Stitch 2.0 in about five minutes.
- 3:01: Why the default AI Studio design looked "vibe coded," and how I brought the Stitch design over.
- 5:17: The PRD gets filled out and the dashboard build starts.
- 6:51: Fixing dead buttons, building the booking flow, and cleaning up the landing page.
- 8:23: Turning on Firebase for authentication and the database.
- 9:08: Stripe payments, publishing, and the recap of where the MVP stands.
Step 1: Pick an idea and pull the PRD from Idea Browser
I picked the On-Demand Tech Support for Seniors idea on Idea Browser. It's a popular one there, and seniors are going to keep needing tech help, especially now that AI is everywhere.
The most useful part of Idea Browser is the build kit, and the most important thing in it is the product requirements document. Without a PRD, your project will probably fail, or at least get harder and harder to build. I treat it as the blueprint for everything that follows. I clicked build, grabbed the prompt, and gave it to Google AI Studio with a simple instruction:
I'm going to give you a product requirements document prompt. I want you to fill it out. I want us to execute on this idea. Help me build this along the way.
Step 2: Design the landing page in Stitch 2.0 first
I cheated a little: before recording, I had already used Stitch 2.0 to generate the landing page and dashboard. It took about five minutes, and the result matched the brand colors and messaging. I like Stitch for getting something out of nothing.
The landing page Google AI Studio made on its own looked okay, but it looked like every other AI-built website. Stitch gives you more control over the design. You can change brand colors, move buttons around, modify, annotate, or regenerate the whole thing. I tried uploading my Stitch zip file into AI Studio, but it wouldn't accept the zip. So I copied the code instead and told it:
I want my website and everything to look like this. Here's the code.
I did this backwards in the video. The order I'd recommend is: start in Stitch for the look, then export from Stitch straight into Google AI Studio's build mode. Idea Browser also has a landing page wireframe prompt you can paste into Stitch to get started.
One note for beginners: Google AI Studio shows a lot of options up front, and it's hard to know where to start. To actually build an app, click Build. If you stay in the playground, you'll get feedback but it won't build the app for you. My Google AI Studio page has more on getting started.
Step 3: Use the PRD as the roadmap and fix what's broken
With the design in place, I gave it the PRD again:
Here's the product requirements document prompt. Fill this out. It is going to be the vision for our project. Let's follow it step by step.
It filled out the PRD and asked what to build next. It offered a tech readiness assessment lead magnet, but I went with the dashboard, and it built a dashboard with a caregiver view. The first version needed work. The "how it works" and pricing sections didn't show up until I asked for them. Member login worked, but other buttons like "book a session" did nothing. So I asked it to take me through the next step that needed polish, and it built the booking flow and connected the dead buttons.
Then I fixed the visual problems. Text wasn't centered, the hero image had odd labels like support_agent, and the "book a $49 one-time fix" button blended into the background. I described each problem in plain English and asked it to redesign those parts so they looked good. The result was much better.
Step 4: Firebase backend, payments, and publishing
Next I asked how to get the app working for real, and AI Studio suggested Firebase as the backend database. I enabled it on the free tier. Since you're already in Google AI Studio, it connects to your Google account, so there's no going off to Supabase, Convex, or Neon to copy API keys and connection strings. It came back with real authentication, database security rules, and booking integration. I also asked it to add an FAQ section.
For payments, it said I'd use Stripe for things like the $49 one-time fix. That needs a secret API key, so it upgraded the project to a full-stack app and set up a redirect to Stripe checkout. I didn't set up a Stripe account or enter keys in this video. As for publishing, the deploy option puts the app in your own Google Cloud project, which requires billing to be enabled. You can still preview the app through the share option.
About 23 minutes in, I had a somewhat working landing page and the MVP was underway. By the end I was about 70% of the way there. Zoom integration and the rest of the support features still need to be built.
Key takeaways
- The flow: Idea Browser prompt → Stitch 2.0 landing page → export to Google AI Studio → give it the PRD → turn on Firebase → add Stripe.
- The product requirements document is your roadmap. Keep going back to it.
- Design in Stitch first if you don't want your site to look like every other AI-built page.
- Expect dead buttons and layout problems. Describe each one plainly and ask the AI to fix it.
- Getting started is the hardest part. Ship something, then improve it. More on that mindset on my vibe coding page.
FAQ
Can Google AI Studio build a landing page without coding?
Yes. In the video I prompt Google AI Studio in plain English to build a landing page, a dashboard, and a booking flow, then fix broken buttons and layout problems by describing them.
Should I start in Stitch or Google AI Studio?
I'd start in Stitch 2.0 for the design, since it gives you more control over colors and layout, then export into Google AI Studio's build mode and give it the PRD.
What backend does Google AI Studio use?
I used Firebase on the free tier. It connects to your Google account and set up real authentication, database security rules, and booking integration without me copying API keys.
Can I take payments in a Google AI Studio app?
Google AI Studio recommended Stripe, which needs a secret API key. It upgraded the project to a full-stack app with a redirect to Stripe checkout, but I didn't enter Stripe keys in this video.
Chapters
- 0:00Intro
- 0:22Idea Browser and the senior tech-support pick
- 0:51Loading the PRD into Google AI Studio
- 1:29Stitch 2.0 landing page reveal
- 2:49AI Studio build versus the Stitch design
- 3:07Copying Stitch code into AI Studio
- 5:04PRD filled out, dashboard build begins
- 6:20Fixing buttons and the booking flow
- 7:42Functioning landing page and MVP milestone
- 8:22Firebase backend setup and booking integration
- 9:20Setting up Stripe billing, and deploying full web app walkthrough
- 34:00Recap and the 70% milestone
Transcript
Read the full transcript
0:00Our whole goal of this video is to be able to go from zero to one as fast as possible and the two tools we're going to be using to do this is one idea browser and the second tool is Google AI studio. So, let's see how many prompts it takes to actually go from nothing to a fully functioning landing page with a fully functioning feature. So, let's go ahead and jump right into it. So, here's idea browser. The one that I chose is on-demand tech support for seniors and this is something that's going to be an ongoing evolution of seniors needing help, especially in today's AI age. So, that's why I chose it. Very popular idea on idea browser. The best part about idea browser is it has this build kit here. The most important part of the build kit is the product requirements
0:45document. Without the product requirements document, your project's going to fail or be increasingly harder to build. So, that's the one thing that I like to pull out of this build kit is this product requirements document right here. You see it? That's the thing that we need, which is going to give us a very detailed that we can take into Google AI studio to start setting the foundation of our actual build. So, I'm just going to hit preview here. Oh, I'm just going to hit build and then we're going to get this prompt here and we're going to have everything built out in Google AI studio. Let's see if we can get this thing built out in like five prompts. So, I'm going to give you a product requirements document prompt. I want you to fill it out. I want us to execute on this idea. Help me build this along the way. Put the prompt in and let's cook. So, while that's happening,
1:30I actually went ahead and cheated a little bit. I'm sorry, but I went into Stitch 2.0 and I started generating, you know, the landing page, the dashboard, how it kind of is all going to work, which I really like Stitch 2.0 for getting something out of nothing. So, basically taking an idea and actually having a physical landing page. This took about 5 minutes. So, really nice, really awesome and obviously, you know, it it aligns with our brand coloring and messaging. Very cool. And these two can connect with each other, which is really nice and use- I will say getting started with Google AI studio in general, just from a person coming in from the AI space, maybe maybe let's just say someone that is just starting to vibe code. They have no idea what to click on. There's too
2:16much going on. Featured, code reasoning chat, image generation, real time. Like, where do I start? It's too much. There's also anti-gravity IDE. So, I'm just giving some feedback here. Where do they start? So, you actually have to click on build to actually build this app out. You know, if you start here in the Google AI studio, it's going to give you some good feedback, but it's not actually going build it out since you are in the playground. Just kind of my point of view on how I would see it from a person that, you know, is just getting into learning these tools. You want to make it as simple as possible, right? And that's just my point of view. So, as this builds out, we will go ahead and then, you know, we don't want that Landing page looks okay. I think that it's very vibe coded looking and it looks like every other AI
3:01website, which is why Stitch 2.0 has a little bit more control over how your website looks. So, let's go ahead and go back and then export. Actually, I already have the zip file. I downloaded it earlier and then let's go ahead and add this in. Upload files. Oh, I can't upload the zip. Well, let's just bring it into AI studio and then I can just give it the PRD again. I'm just going to close this one. Copy this prompt again. I'm kind of doing it backwards, but I would definitely start starch start your build inside of Stitch 2.0 for just kind of how you want it to look. You could play around with a lot of the brand coloring, where the buttons go and and such. So, I like that. Modify, annotate.
3:46You could just regenerate the whole the whole system if you wanted to. I like what we have so far. Really simple, easy to read, but it's going to regenerate the the design while we build this out. Interesting. That's not what I had. Very interesting. Wait. Let's see if I just copy the code. I want my website and everything to look like this. Here's the code. Pre-pro anyways. Pro preview. Okay, now we're cooking. Here's the product requirements document prompt. Fill this out. It is going to be the vision for our project. Let's follow it step by step. So, ideally you want to start in Stitch 2.0 first with the design and then go from there. In idea browser, it does have landing page
4:32wireframe prompt. So, you could possibly get that to Stitch. I wonder how that would do. Go back. Let's see if it would work with Stitch. Just see what it cooks up. The goal is to go from zero to one as fast as possible. We're not trying to reinvent the wheel here. We're just trying to get your idea into the physical world as fast as possible with as less resistance as possible. We want things to work as well. And if we could publish a buy button on this thing, even better. So, cool. It filled out the PRD. That's awesome. Cool. All right. Great. What is the next step? The how it works and the pricing doesn't come up. Cool. All right. I had to tell it that. That's fine. Kind of jank. We'll just
5:17leave it. We'll leave it. Let's just see how fast we could get it going. Okay, awesome. It says the tech readiness assessment lead mag. Let's do option two, the dashboard. Awesome. So, it built us that landing page off of this prompt. Hmm, not bad. So, basically taking that prompt into Stitch 2.0 first and then exporting it into the build. It export into AI studio build. So, build with AI studio and then you could start adding in that product requirements document, building out the dashboard. If you can go from idea to landing page to working features in just under 10 prompts, that's going to be huge for people to start iterating on their project. People start to worry too much about, oh, my
6:03brand coloring, logo design. This is just going to help you get something up, put into production right away. And that's the whole point. Nothing's going to be perfect. You need to at least get this thing shipped and then iterate as you go. That's why we're using this AI studio because it seems like it's the fastest to get your idea off the ground. So, it seems like it did the dashboard, caregiver view. Okay, interesting. Okay, so let's publish. Let's set up billing, right? All right. Hmm, okay. Hmm, interesting. The dashboard. Buttons don't work. Hmm, needs a lot of work. Close. Okay, member login works, but it seems like the other buttons don't work like book a session. Take me through the next step that needs this more polished.
6:51Okay, so it built the booking flow and wired up the dead buttons. Cool. Can we double-check the buttons on the landing page? They look kind of off and the text isn't centered and there's a lot of underscores in the hero image. It says support_agent. Just looks weird. Can you redesign that to make it look aesthetically pleasing? Okay, the button that says or book a $49 one-time fix, the button blends into the background much. I don't know. I'm I'm being a little picky, but I want it to look good. Mainly the buttons work actually, can publish a buy button and get this thing operational. To publish it, I will need to set up a Google Cloud project. Not letting set up billing. Does not have billing enabled. Yep, much
7:36better. Okay. All right. All right. Awesome. All right. Let's go. Okay. Cool. What are the next step to get this functioning? What about pushing this like publishing it? It says it needs a my billing information. Is there easy way to publish this easier? And yeah, set up Firebase. Firebase is going to be the back-end database. I like this so far. Just getting used to how this all works. Essentially, what we want to do is be able to pull ideas from idea browser, you know, basically have like a build button or something like that, right? And like build this idea. See, we got it right here. So, to be able to take an idea, go to Stitch, build the landing page, go from Stitch, hit export, hit Google AI studio, build an AI studio,
8:23put in the product requirements document and start to see this come to life. So far, we're at 23 minutes in and we have a somewhat functioning landing page and our MVP is being built. So, enable database. To enable to continue with Firebase, we're doing the free tier. Enable Firebase. That's easy. I like that. Don't need to go to the Superbase, Convex, or Neon to plug in your API keys and your connection string. If it just happens all here, very nice. Cool. I think adding a FAQ section would be helpful, too. So, it's wiring up all the back-end database, which is really helpful. So, we can actually, if we were to publish this live, we can actually start getting users and then we would need to publish a buy button somehow. Hopefully, they have that integrated somehow with Stripe or some payment
9:08option would be nice. Wow, it's done. Real authentication, database security rules, booking integration. Now, that is nice. I like So, I just trust that it works. Let me ask about payments. How do we integrate payments on this page? Very cool. To integrate real payments like the $49 one-time fix, we use Stripe. Okay, before processing payments requires a secret API key. Upgrade to a full-stack app. I will do this. Okay. Okay. Okay. Redirect to Stripe checkout. Okay. Okay. Yes. And then I don't know if it answered question. Regarding publishing, you're likely looking at the deploy option, which deploys the app to your own Google Cloud project, which does require billing. Go to share. See, we want to
9:54share default full screen. Let's see if we can go down. Oh, I see. Cool. Very cool. Ah, here we go. Very cool. So, it does have authentication going. Cool. So, it's now it's building out the full web app. Wow. So, you could essentially go from zero to one in under 30 minutes. Never have used Google AI Studio before. It's pretty cool. You can crank out apps like this. Getting them to work is the next thing, but this was the hard part. Getting started is the hardest part for every single one building in this space. So, if you use that flow, like going through Stitch to build out the landing page from idea browser prompt that they give you, you can go to Stitch, enter that prompt, get the landing page going, export to Google AI Studio, build. Once
10:39it builds the actual landing page out, then you go in and you prompt it with the PRD, and that's the road map for your project. And then, you go ahead and set up Firebase for your back end, which automatically connects to your Google Gmail account since you're using Google AI Studio. And now we're on the payment part where I would then need to go set up a Stripe account and put in my keys, which I'm not going to do that in this video, but that's pretty cool. That's pretty cool. Within 30 to 35 minutes, you can have a functioning We're about 70% of the way there cuz we still need to integrate Zoom and all the features that this would offer for helping seniors with tech-related issues. Um, look, fix this for iPads, TVs, printers, and more. That's pretty cool.
11:24I like that.
Ready to start building with AI?
Join the Shipping Skool community free. Paid members get live bootcamp calls every week and weekly-updated courses.
Join Shipping SkoolKeep reading
How to Build an AI Audiobook App with Google AI Studio (No Coding)
I use Idea Browser's build kit prompts (brand packaging, landing page, PRD, feature spec) in Google AI Studio with Gemini 3.1 Pro to build Echo Sync, an offline audiobook maker. In about 30 minutes it has three landing page designs, an upload-to-audio flow, and Firebase sign-in with a seven-day free trial.
How to Build an App with Google AI Studio in 22 Minutes (No Coding)
I used Idea Browser to pick a validated idea and Google AI Studio to build Before You List, an app that scans real estate listing photos for AI edits and writes the required state disclosure. It took about 22 minutes and no coding.
Google AI Studio Tutorial: Build a Car Restoration App (No Code)
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.
