Palmer scopes a map-first app for parents, with nearby activities, filters, and eventually favorites and user accounts. He uses AI and web research to discover OpenStreetMap data, then gives Replit Agent a mockup, framework documentation, and sample API data as context.
Complete Vibe Coding Tutorial: Build a Full Stack App in 30 Min with AI
Speaker
Matt Palmer, head of Developer Relations at Replit, shows Peter Yang how to build a family activity finder with Replit and shares practical lessons on prompting, debugging, and vibe coding.
Palmer recommends keeping prompts concise, specifying the desired result, and working through features one at a time. He tests the map, filters, search, and directions, checks logs when something fails, and uses checkpoints to preserve working versions. When search turns out to be disabled, he gives the agent that specific finding to fix.
The demo adds Replit authentication and a database so users can save favorite places and mark them visited. Palmer checks the app’s requests and database when the favorites page returns a 404 and location names are missing, then uses Replit’s security scanner to find issues before deploying. The deployed app uses the same database as the preview.
Palmer says AI results vary, and polished demos hide the trial and error behind them. He advises builders to experiment, debug, and start over when needed; after a stuck attempt, they can ask AI what they learned and include that in a fresh prompt. He also describes learning web development by inspecting and asking questions about AI-generated code.
Palmer expects agents to work for longer stretches while people supervise, make architectural decisions, and step in when needed. He says successful builders take initiative, stay curious about improving their product, and have the courage to fail and try again. Peter Yang emphasizes that AI can help people who do not see themselves as engineers learn by building.
Takeaways
- Give the agent a mockup, relevant documentation, and sample data to ground its work.
- Start with a small working version, then add and test features one at a time.
- Use logs and specific error details to guide debugging; keep checkpoints so you can return to a working version.
- Review data structures before adding features that depend on them, such as favorites and visited status.
- When repeated fixes stall, ask what the attempt revealed and carry those lessons into a fresh start.
Mentioned in this talk
Search inside this talk
What was claimed 7
- feature
Replit Agent: Plans, builds, edits, and debugs applications
“you’ll notice it editing files and debugging on its own”
YouTube Unverified1 source· Talk
- role atMatt Palmer is Head of Developer Relations at
Replit
“My guest today is Matt Palmer, head of Developer Relations at Replit.”
YouTube Unverified1 source· Talk
- feature
Replit: Provides a cloud-based code editor and development environment
“you’re getting an entire code editor and development environment”
YouTube Unverified1 source· Talk
- integrates with
“a partnership with a great security company called Semgrep”
14:45inHow Replit Went From $10M to $100M ARR In Just 9 MonthsYouTube Verified2 sources· Talk
- feature
Replit: Integrates databases and authentication into the platform
“Replit has added a bunch of services that integrate directly into the platform, ... databases and auth”
YouTube Unverified1 source· Talk
- feature
Replit: Allows users to deploy a snapshot of their development environment
“I can take a snapshot of what I just built and deploy it live to the internet”
YouTube Unverified1 source· Talk
- feature
Replit: Provides security scanning for applications
“we released this last week: our security scanner”
YouTube Unverified1 source· Talk









