Abdallah | Build Apps with AI

I'm a pharmacist who got bored and started building apps with AI. No CS degree. No coding bootcamp. Just Lovable, Supabase, and a lot of failed prompts. This account is my build log. Prompts that work. Mistakes I made. Apps I shipped. Follow if you want to build real things with AI 👇

Introducing skills in Lovable.

@FPLMatthew @FPL_TomHadley Have you played your TC chip?

DGW36 #FPL 80 points and a red arrow to 10,479 OR unless the Grim Reaper @FPL_TomHadley tells me I’ve lost some points!

We made great design 4x easier Introducing Lovable Asthethics 🎆 The biggest bottleneck in building pretty websites isn't the code, it's getting the layout, typography, and colors just right.

Introducing the Lovable aesthetics update, a new level of design in vibe coding. Ask for typography, layout, and color preferences. Preview design concepts before building, and create bolder landing pages, apps, and blogs.

5 Lovable features that will take you from just a product to a product people use:

Wiz security scanning is now natively integrated into Lovable, extending your Wiz policies to every Lovable project. Here's what that means in practice: When someone on your team builds an app in Lovable, Wiz scans run alongside Lovable's built-in security checks. Findings surface right in the security view with severity, remediation steps, and a direct link into Wiz for deeper investigation. Everything flows back into your Wiz Code and Build scans page, so your security team has full visibility. For developers: fix issues without leaving Lovable. For security teams: Lovable projects show up alongside everything else you monitor in Wiz. For leadership: no blind spots, no shadow IT - governance follows your teams wherever they build. If you're already on Wiz, connecting takes just a few minutes.

Today we’re releasing the Lovable MCP server in Research Preview. Create, iterate on, and deploy apps directly from your terminal or AI agent. Available now.

A first step towards something much bigger :)

the lovable mobile app is here. build wherever you are

What nobody tells you about shipping your first app: It won't be perfect. The design will be off. Some features won't work right. You'll see 10 things to fix immediately. Ship it anyway. A live imperfect app beats a perfect app that doesn't exist. Every. Single. Time. What are you waiting to ship? 👇

I gave Lovable one sentence. "Build me a SaaS landing page for a productivity app targeting freelancers." In 4 minutes I had: → Hero section → Features section → Pricing cards → CTA button → Mobile responsive 4 minutes. The only skill I used was knowing what I wanted. That's the whole secret.

Exactly how I structure every new Lovable project: Week 1 — Foundation → Homepage + navigation → Auth (login, signup, protect routes) → Database tables + RLS Week 1 — Core feature → The ONE thing the app does → Nothing else Week 2 — Polish → Mobile responsive → Empty states → Loading states → Error messages Week 2 — Launch → Custom domain → Stripe checkout → Share it publicly Most people skip the foundation. Then wonder why everything breaks. Build boring. Ship fast.

Exactly how I structure every new Lovable project: Week 1 — Foundation → Homepage + navigation → Auth (login, signup, protect routes) → Database tables + RLS Week 1 — Core feature → The ONE thing the app does → Nothing else Week 2 — Polish → Mobile responsive → Empty states → Loading states → Error messages Week 2 — Launch → Custom domain → Stripe checkout → Share it publicly Most people skip the foundation. Then wonder why everything breaks. Build boring. Ship fast.

The order matters more than the prompts. Wrong order: Design → Logic → Database → Auth Right order: Structure → Auth → Database → Logic → Design I learned this the hard way. Built a beautiful UI, then spent 3 days breaking it trying to add auth. Build boring first. Polish last. Always.

The 3 tabs I always have open when building with Lovable: 1. Lovable — obviously 2. Supabase dashboard — watching data appear in real time 3. My app in preview — checking everything didn't break That's it. That's the whole setup. What does yours look like? 👇

3 things I wish I knew before using Lovable: 1. Always describe the full context not just what you want changed 2. Screenshot errors before prompting "fix this" means nothing 3. Build ugly first design last Save this 🔖

Hot take: Knowing how to prompt is the most valuable skill of 2026. More valuable than coding. More valuable than design. The people learning this now will be untouchable in 2 years. Are you learning it?

Nobody talks about this Lovable trick: When your UI looks broken, don't re-prompt. Just say: "Do not change any logic or functionality. Fix only the visual layout of [specific section]. Keep everything else exactly the same." Saves you from breaking things that already work.

Supabase + Lovable confuses everyone at first. Here's the only setup guide you need: Step 1: Create project on supabase.com Step 2: Copy your Project URL + anon key Step 3: In Lovable → Integrations → Supabase Step 4: Paste both keys Step 5: Tell Lovable: "Connect auth using the Supabase project I just linked" That's it. You're connected. Save this 🔖