For vibe coders

Documentation Index

Fetch the complete documentation index at: https://notikaai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

If you’re building with Cursor, Lovable, Bolt, v0, Replit, or Figma Make, Dreamlit handles every notification your app needs to send. Each AI specializes in what it does best. Your app’s AI focuses on the product itself, and Dreamlit’s AI focuses on the emails (and other messages) your app sends to users. A smaller job per AI means fewer frustrating loops and better results across the board.

​

Why do notifications break the vibe coding flow?

Notifications are where an AI-built app usually stalls. The AI happily generates screens, buttons, and database logic, then hits email and things fall apart.

• Previewing and testing is painful. There’s no easy way to see what an email will actually look like, or to test it against real user data before going live.
• Behind-the-scenes plumbing piles up. Sending emails usually means adding scheduled jobs, small server functions, and connectors between different services. None of that is the app you set out to build.
• Setup takes forever. Getting a single email working usually means wiring up an email server, verifying your domain with DNS records, juggling API keys, and configuring webhooks. It’s a lot of clicks and copy-paste.
• Email design is its own rabbit hole. AI can write code, but email layouts behave nothing like a regular web page. Making your email look right across Gmail, Outlook, and Apple Mail is a craft on its own.

​

How does Dreamlit fit into a vibe coding stack?

Dreamlit plugs into the Supabase or Postgres database your app already uses, then vibe-codes your notifications the same way Lovable or Bolt vibe-codes your app. Your app’s AI stays focused on the product while Dreamlit’s AI handles messaging from start to finish.

​

Guided setup

A short flow connects your database and sets up your sending address. You don’t need to configure an email server, manage API keys, or wire up any behind-the-scenes integrations yourself.

​

Describe what you want, get a workflow

Tell Dreamlit in plain English what you need. “Send a welcome email when someone signs up,” or “email users their invoice after a successful payment.” The Workflow Agent handles the rest, including when the email should send, what it should say, and how it should look. Dig into the details whenever you want finer control.

​

Zero integration overhead

Your app writes to the database the way it already does. Dreamlit securely connects to that same database and reacts to changes, so your app stays clean and the AI building your app doesn’t have to juggle email logic alongside everything else.

​

Production-ready templates

Dreamlit generates polished email designs that look great on both desktop and mobile, well-written copy, and the logic for tricky cases like automatic retries if a send fails. Skip the “test test test” emails to yourself.

​

Preview with real data

See exactly how an email will look to a real user, using live data from your database. No more placeholder content or fake test data.

​

What notification workflows work well for AI-built apps?

Vibe-coded apps tend to need the same handful of notification patterns. Dreamlit covers each one. For platform-specific walkthroughs, see the guides for Lovable, Bolt, Cursor, v0, Replit, and Figma Make.

​

Start shipping notifications

​

References

• How Dreamlit’s database-driven architecture works
• Supabase Auth emails guide
• Supabase default SMTP is not production-ready

---

Last validated: 2026-04-20