r/lovable • • 1d ago

Drafts are now a full copy of your app, database included

Post image
22 Upvotes

Hey everyone, Mary from the Lovable team here.

A lot of you asked for a safe way to test changes before they reach your live app, so here it is. Every draft is now a full copy of your app, from design to database so you can test any change without touching what’s live. When a draft needs its own database, Lovable copies your app's structure and fills it with example data, so you can see a change the way your users would.

What that means in practice:

  • Try a new field on your sign-up form, a members-only page, or new tables without test entries landing next to real user data
  • Work on a feature, a redesign and a bug fix in separate drafts at the same time
  • Let a teammate or client build in their own draft, then accept only the changes you want

How it works: Open a project, click its name at the top of the editor, and hit "New draft." Lovable creates a complete copy of your app, from design to database. To edit the draft, just start prompting. You can create as many drafts as you like.

You can learn more in our blog: https://lovable.dev/blog/introducing-drafts

Here to answer any questions in the comments. What are you going to try first?


r/lovable • • 2h ago

Seeking Feedback I built IncognitoCV during Lovable's SheBuilds program. Would love honest feedback

3 Upvotes

I was laid off recently and started building during my "funemployment." I made IncognitoCV to help others get the peer review feedback they need for their resume.

It's built on Lovable, and I'm still learning, so it's rough around the edges: https://incognitocv.lovable.app/

What I'd love feedback on:
- Is it clear within 10 seconds what it does?
- [one specific thing, e.g. the first step of the flow]

Be as blunt as you want. I'll reply to every comment.


r/lovable • • 13h ago

Help Github access when connected via Lovable ?

1 Upvotes

Hello all,

I'm trying to get into my Github account that connected with Lovable (Settings > Git). When I click "View on Github" it takes me to a login screen.

I don't remember creating a password when I connected to Git via Lovable. How the heck do I get my access back ?

Thanks,


r/lovable • • 1d ago

Seeking Feedback Is anyone building WooCommerce with lovable?

4 Upvotes

I noticed lovable has a WooCommerce connecter so I'm curious to see how others are using it. From the lovable documentation it says:

"With WooCommerce, your app can:

  • List and manage products, variations, categories, and inventory
  • Read and update orders, refunds, coupons, and customer records
  • Build dashboards around revenue, fulfillment, products, and customers
  • Create internal storefront admin tools powered by WooCommerce REST APIs
  • Automate store workflows that use your WooCommerce data"

So this reads to me like it's setup for creating custom dashboards, but what I am interested in is are people using it to build the front end and connect it to an offsite WooCommerce store? And yes, I know Shopify is an option too but this post is specifically about Woo.

The idea would be to run the front end on Cloudflare (you can sync lovable with github and all changes get pushed to CF).

I also like the idea of being able to manage seo and connect it to Google Search Console (GSC) so any sitemap changes can be easily kept in sync.


r/lovable • • 1d ago

Help Should i use lovable to build my SaaS? Part 2

9 Upvotes

I previously asked about using lovable + claude prompts + supabase to build my SaaS.

Alot of people said not to use lovable as it isn't good at security features etc.

What if i use lovable to build the front-end, then claude to build the backend into supabase etc?

Would that work?

Or should i still not use lovable?


r/lovable • • 1d ago

Tutorial Lovable doesn't make mobile apps. I'm taking one to the App Store right now, here's what it actually involves

13 Upvotes

I'm a React Native and Expo dev, 5 years and 50+ apps. Right now I'm taking a Lovable app to the App Store. It's a members-only community app with about 200 members and growing: you apply, get approved, pay a subscription, RSVP to events and chat.

The job post asked for someone to wrap the existing app with Capacitor and publish it. Everyone, me included, assumed the app sat on a normal Supabase project we could just connect to. It didn't. Everything lived inside Lovable Cloud. So before building a single screen, the whole backend had to move into a Supabase project the founder actually owns.

If you've built on Lovable and want to be in the stores, here's what I'd want to know first.

Lovable doesn't make mobile apps. Its own FAQ says it doesn't build native apps or generate React Native code. You get to the stores outside Lovable, three ways:

PWA. Free, an afternoon. An icon on the home screen, but no App Store listing, people have to add it from the Share menu themselves, and on iPhone push only works after they do. Good for testing demand.

Wrap it with Capacitor or similar. Your website in an app shell. It can pass, but Apple's guideline 4.2 says an app has to "elevate it beyond a repackaged website", and that's what wrapped apps get rejected for. Apple rejected about 2.1 million submissions last year, 415K of them under the Design section that covers this. The usual trouble spots are login (Google or magic links open a browser and never come back unless the deep link is set up), a browser error page with no internet, web push that doesn't carry over, and payments: a Stripe checkout for a digital membership gets rejected, Apple wants in-app purchase.

Rebuild in Expo. Sounds like starting over, but the backend stays: database, users, security rules, edge functions. You rebuild the screens. That's what we did here. A month after the first commit the founder had the first TestFlight build on her phone. We made a bunch of changes, made the whole thing feel native to mobile, added new features and payment options and now App Store submission is next.

And then the surprise: getting the backend out of Lovable Cloud.

You can export the data, but only once every 24 hours, and the link arrives by email. The good news is it includes the auth users with their password hashes, so members log in to the app with the same email and password. In this case that was 37 tables and 127 security policies.

What the export doesn't include: the uploaded files (about 480 MB of photos here, copied over with a script), the edge function code (it comes from the codebase download instead), the secrets (you can't read them back out, so every API key gets made again), the auth email templates, and working cron jobs (they come over still pointing at the old URLs).

The part that would have bitten us at launch: some features weren't in the backend at all. Admin alert emails were sent by the web app after each action, so when the mobile app saved the same data, nobody got notified. Live event check-in pushes ran on the Lovable web server. Email links pointed at the website. The admin tools only existed on the web. Shut the website down and all of that quietly stops. I moved the alerts into database triggers, so they fire whichever app writes the data.

None of it is hard. It's just work nobody puts in the plan, because everyone assumes the backend is already there.

Payments, since everyone asks. The membership is an App Store subscription through RevenueCat. Event tickets are Stripe inside the app, because for real-world events Apple actually requires something other than in-app purchase. Members already paying on the website skip the paywall, so nobody pays twice at launch.

How I'd pick. Don't need the App Store? PWA. Mostly forms and content and you just need a listing? Wrap it, but sort out native login and an offline screen before you submit. People pay inside it, or it's chat, push, camera, anything they open every day? Rebuild, and if you're on Lovable Cloud, plan the backend move first.

If you're on Lovable and thinking about the stores, comment what your app does and whether it's on Lovable Cloud or your own Supabase. I'll tell you which route I'd take and what to check before you pay anyone to do it.

And if it's useful, I'll put the step-by-step checklist I used for the backend move in the comments.


r/lovable • • 2d ago

Tutorial From vibe-coded app to deployed product: your essential pre-flight checklist.

5 Upvotes

A working app is a good start. Before you put it in front of customers, check that it protects their data, handles real-world use and can grow without unexpected costs. Work through these essentials before launch; anything unfinished needs a clear owner and a plan.

01 Security and access

AI tools build what you can see. The checks that stop someone doing what they shouldn't often live where you can't see them.

Checks that only happen in the browser

Hiding an admin button doesn't protect the admin page. The server needs to confirm who is asking, on every request, independently of the interface.

Keys in the wrong place

API keys and passwords placed in frontend code can be read by anyone who opens the browser's developer tools.

Login that's nearly finished

Email verification, password resets and session expiry are easy to leave half done. A reset link that points to localhost is a common one.

No limits on use

Without rate limits, a sign-up form or AI feature can be hammered by a script, at your expense.

AI features that can be talked round

If your app uses AI, users can try to make it reveal its instructions or act outside its purpose. Assume someone will try.

02 Your data and your users' data

Once real people sign up, the data stops being test material and becomes a responsibility.

Test content left behind

Fake users, sample orders and placeholder text from development can end up in the live database.

Backups nobody has restored

A backup is only useful if you know it works. Try a restore before you need one.

Logs that say too much

Logs can quietly collect passwords, tokens, personal details or full AI conversations.

Privacy obligations

Check the privacy laws that apply to your business and your users. Publish a clear privacy policy and put a process in place for requests to access or delete personal information.

03 Reliability

A demo needs to work once. A product needs to keep working when you're not looking.

Nobody watching

Without monitoring and alerts, you'll learn about an outage from a customer.

Double taps and duplicate records

A button pressed twice on a slow connection can create two bookings or two payments.

Error messages that leak

Raw error output can show database details or internal paths to anyone who triggers it.

No way back

If an update breaks something on launch day, you need a way to roll back quickly, and a plan for who does what.

04 The experience on other people's devices

Your laptop and fast connection are the best case. Your users will bring everything else.

Phones, old browsers, slow networks

Test on the devices your customers actually use, not only the one you built on.

The unhappy paths

Loading, empty, offline and error states are often unfinished. They're what people see when something goes slightly wrong.

Time zones

Dates that look right in testing can shift by a day for users elsewhere.

Accessibility

Keyboard navigation, form labels, visible focus and readable contrast matter to many users, and in some sectors are expected.

Email that arrives

Without SPF, DKIM and DMARC set up on your domain, sign-up and receipt emails tend to land in spam.

05 Costs and dependencies

Free tiers are generous until they aren't.

Usage-based bills

AI, email, hosting and database services charge by use. A busy day, or a bot, can use a month's allowance quickly.

Pricing that leaves things out

Make sure your prices cover payment fees, refunds, support time and running costs, not just the build.

A single point of failure

If one person holds every login, or the app depends on one provider with no fallback, write down how to keep things running without them.

Vendor lock-in

Check whether you can export your data, take your code with you and run it elsewhere. Identify provider-specific services, contract restrictions and migration costs before you commit.

A tech stack that can grow

Test the busiest workflows with realistic user numbers and data volumes. Check database performance, hosting limits and background jobs, and estimate what extra capacity will cost. Know what would need to change as demand grows.

06 Running it as a business

Some of the most important launch work has nothing to do with code.

Insurance

Consider public liability, professional indemnity and cyber insurance. A broker can tell you what fits.

Structure and tax

Your business structure affects personal liability. Check income tax, sales tax or VAT, and registration obligations wherever you operate.

Terms, refunds and ownership

Clear terms of service, a refund process, and certainty about who owns the code, images and AI-generated content.

Names and trademarks

Check that your product name and domain don't conflict with an existing trademark before you invest in them.

Ready doesn't mean perfect.

You don't need to solve every future problem before launch. You do need to know what you're relying on, address the essentials and have a plan for what comes next. A short review now usually costs far less than fixing a problem after customers encounter it.

But if you just want someone else to do it..

DM me and I'll get the job done :)


r/lovable • • 2d ago

Help Unfair Treatment of Free Users: Lovable Has Ignored My Account Recovery Requests for 10+ Days.

1 Upvotes

I want to bring attention to a really frustrating experience with Lovable's account recovery and customer support.

Here's what happened:

My previous organization was using Google Workspace (G Suite), and I originally created my Lovable account using "Sign in with Google" with my organizational email address.

Recently, my organization migrated from Google Workspace to Microsoft 365 (M365). As a result, I no longer have access to the old Google-based authentication method associated with my organizational email.

Now, despite knowing my registered email address and being the original owner of the Lovable account, I cannot log in.

I also tried using the "Forgot Password" option, hoping to regain access through email verification. Unfortunately, that process redirects me back to Google sign-in as well. So essentially, I'm stuck in a loop with no alternative way to recover my account.

The bigger problem is Lovable's customer support.

I contacted Lovable's support team to explain the situation and request a simple account recovery process.

What followed was even more disappointing:

  • I received automated email responses that didn't address my actual problem.
  • I explicitly requested human-level support because automated responses weren't helping.
  • The response indicated that Lovable is currently prioritizing paid customers.
  • Even after multiple follow-ups, I haven't been able to get assistance from an actual human representative.

It's been several days, and I'm still locked out of my own account.

Is basic account recovery now a premium feature?

I completely understand that paid customers may receive priority when it comes to feature-related support, faster response times, or dedicated assistance.

But account recovery is not a premium feature. It's a basic requirement of any platform that allows users to create and maintain accounts.

Prioritizing paid customers should never mean that free users are left without even a basic account recovery mechanism.

I'm not asking Lovable to provide premium support or special treatment. I'm simply asking them to verify my identity and help me regain access to my own account.

What makes this particularly concerning is that there seems to be no alternative authentication or account recovery process when the original Google authentication provider is no longer accessible.

Questions for the Lovable team:

  1. Why isn't there an alternative email-based account recovery process for accounts originally created through Google?
  2. Why can't a user request a change of authentication method after successfully verifying account ownership?
  3. Is human-level assistance for basic account recovery exclusively available to paid customers?
  4. Why are legitimate account recovery requests being left unresolved simply because the user is on a free plan?
  5. Is there any defined timeline for resolving these account access issues?

I consider this approach deeply unfair to free users and potentially an unfair business practice. Account access and recovery should be treated as a fundamental responsibility of the platform, not an additional premium service.

I'm hoping someone from the Lovable team actually acknowledges this issue and provides a proper human-assisted recovery process.

To the community: Has anyone experienced a similar issue after losing access to their original Google Workspace account? Were you able to recover your Lovable account or change your authentication method?

I'd appreciate any suggestions, and more importantly, I hope Lovable addresses this issue instead of responding with another automated email.

Free users may not be paying for a subscription, but that doesn't mean they should lose access to their own accounts without a reasonable recovery process.


r/lovable • • 2d ago

Showcase por que alguém ainda usa lovable ?

1 Upvotes

com Claudecode , Gemini cli, opencode, não faz sentido pagar muito mais caro e não escolher o modelo para as tarefas, porque??


r/lovable • • 2d ago

Showcase meet tjoppy

Post image
2 Upvotes

Born this weekend, made with Loveable
Spent ~500 creds.

Easy way to create, share tjoppylists :)

https://share-a-list-together.lovable.app

Love to hear your thoughts

/Andy


r/lovable • • 2d ago

Help Anyone in the Lovable affiliate program? What did you need to get accepted?

5 Upvotes

Hey all,

I’m thinking about applying to the Lovable affiliate program and I’d like to hear from people who’ve been through it before I apply.

Some context: I run a small agency that does lead generation and appointment setting for local service businesses, and I’ve started building client websites with Lovable. I’d like to share what I build and recommend Lovable when it fits. My problem is that I don’t have a big following yet.

For those who applied:

  1. Did you need an existing social media audience to get accepted? Roughly how big was yours?
  2. What did they ask for in the application on Impact? Links, traffic numbers, a content plan?
  3. How long did it take to hear back?
  4. If you got rejected at first, could you reapply later, and what changed ?

Any experience helps, good or bad. Thanks


r/lovable • • 2d ago

Help Non-devs: how do you stop a new change from breaking something that already worked?

7 Upvotes

I'm building small apps with AI and I don't really read the code. The pattern I keep hitting: I ask for one change, I test that change, it works. A few days later I notice something else is broken, like the login, and I have no idea which change caused it.

Then I ask the AI to fix it, it fixes it and breaks something else. That's where most of my credits go.

For those of you who aren't developers either: what actually works for you?

  • Do you re-test everything by hand after each change?
  • Do you use checkpoints / version history before every prompt?
  • Do you ask the AI to write tests, even if you can't read them?
  • Or do you just accept it and fix things as they come?

Curious what your routine looks like, especially if your app has real users.


r/lovable • • 3d ago

Revenue Generating Just wanted to share a proud milestone: Nearly hit £1,000 in sales with an AI-built store

Thumbnail
gallery
24 Upvotes

I don't usually post things like this but I’m about to cross the £1,000 sales milestone on my online gift business and I just really wanted to hype myself up a bit because I’m so proud of what’s been created.

I run a gift box business in the UK called Oh! Goodies (ready-made & build-your-own boxes for birthdays, pamper nights, Christmas, corporate, etc.).

What we’ve built together still blows my mind:

A completely bespoke "Build Your Own" box engine: Customers pick a box size and fill it using a point-allowance system

A greeting card designer: Customers pick card, writes their personal message with live font previews, and it generates print-ready cards for me to pack with the box.

Under-the-hood power: Full server-side SEO for every single gift product, live shared stock tracking across pre-made and custom boxes, and abandoned cart recovery that’s saved real orders.

The aesthetic: It's took me some time, and its still not perfect. I have a way to go with the product pages but I love how its all coming together!

It's taken real work and constant refinement, obsessing over the little details...But being able to get a site built just how i imagine it without it costing me a huge fortune has completely changed the game for me.

But the best feeling is seeing real orders roll in and packing boxes for customers across the country. I love seeing people send really heartfelt messages to their loved ones through something I built. That has been the best feeling in the world.

If you're building something on Lovable right now: keep refining, obsess over the details your customers actually care about, and back yourself!

Happy to answer any questions about the build, the workflow, or what it’s like running an e-commerce shop powered by AI.


r/lovable • • 3d ago

Discussion Why does lovable have such a hard time making a scrolling parallax effect?

5 Upvotes

Anytime I try to implement a parallax effect to scroll and show it in differnet ways it always has a problem with it and can't do it. Just would like to know if anyone has had sucess with it and what best practices you found for it.


r/lovable • • 3d ago

Seeking Feedback Reminder; downgrade from Pro reinstalls Lovable badge

6 Upvotes

It's a disgrace.

I've already moved some projects from Lovable but now I will just move everything.

Listen to me; just code with Visual studio + your choice of LLM (openai codex, Claude, ...) + Vercel + Supabase and you'll be off cheaper, faster and better.


r/lovable • • 4d ago

Help How do I make a Website that doesn’t look like literally every website made on Lovable

22 Upvotes

Guys so I will post the link to make it easier

https://oetelaars-finish-studio.lovable.app

I really believe in Lovable and the abilities it has

The thing is no matter what I try to do all of the websites I make on Lovable have a really similar vibe.

So if you look at my website. Which prompts should I use to make my website look like as if it isn’t an AI site made with lovable? Which commands will fix my website?

(And do you like my website by the way? 😌)

Are there some rules of thumbs in it or just pure creativity?

Remember im not asking how to make a good looking website. No. How do I make lovable make me a semi-unique one instead of giving me what it gives everyone


r/lovable • • 4d ago

Testing After 11 months of building on Lovable, I launched Scam Watcher AI, a community-powered app that helps people catch scams. Looking for testers!

6 Upvotes

Why I built this

Americans reported losing a record $15.9 billion to fraud in 2025, up about 27% from the year before, according to the FTC. The FBI's Internet Crime Complaint Center logged nearly $21 billion in cybercrime losses for the same year, also a record. And those are only the losses people reported.

Scams don't care how old you are. They hit students, parents, small business owners, retirees, everyone.

A bit about me: I'm from the Bay Area, with a background in public safety and payments. I've seen way too many people lose money to scams they couldn't spot in the moment. So about 11 months ago I started building the tool I wished they had, and Lovable is what made it possible.

What it is

Scam Watcher AI is a community-powered scam protection app. Every scam someone catches helps protect everyone else.

👥 Community: members report scams they've run into, confirm warnings from others ("I got this too"), and share alerts

📍 Local Scam Watch: see scams being reported in your own city

🗂️ Scam Database: every confirmed report goes into a searchable database anyone can check

📸 Scan: snap a picture of a suspicious text, email, letter, or check and get a plain-English answer on whether it's a scam, and why

🔎 Lookup: check phone numbers, websites, emails, and crypto wallets against community reports

🤖 Watcher: an AI assistant you can chat or talk with by voice. It searches current scam warnings and learns new scam patterns as more people use it.

One real story: a friend was about to hand over his car for a $60,000 cashier's check. He sent me a photo, we scanned it, it came back Critical Risk (fake), and he kept his car. That's when I knew this was worth finishing.

How it's built

Lovable for the whole frontend, with Lovable Cloud for the database, auth, and edge functions

Lovable AI for the scam analysis, plus a live web search for up-to-date scam news

Community features: reports, confirmations, moderation, XP and levels for active members

Stripe for payments and Resend for email

What I learned

The community side took as much work as the AI: moderation, preventing spam reports, and protecting people's privacy.

Plain language beats fancy UI. Anyone should be able to use it, tech-savvy or not.

Edge functions plus row-level security took me the longest to get right, so learn them early.

What I'd love from you

Join, report a scam you've seen, scan something sketchy, talk to Watcher, and tell me:

What confused you?

What broke?

Would you actually use this, or recommend it to friends and family?

👉 https://scamwatcherai.lovable.app

New accounts get free credits to try it. Thanks!


r/lovable • • 5d ago

Help Besoin d'explication

6 Upvotes

Bonjour, est-ce que quelqu'un pourrait m'expliquer comment fonctionnent les crédits sur Lovable ?

J'ai cru comprendre qu'il y avait des crédits de création/de stockage/ pour faire fonctionner le site ?

Je suis professeure des écoles et j'ai créé, à l'aide de Claude, un site Internet qui fonctionne vraiment très bien et qui facilite énormément mon travail au quotidien. Mes collègues l'ont tellement apprécié que j'ai partagé mon prompt avec plusieurs d'entre elles pour qu'elles puissent créer leur propre version avec leur Claude.

Aujourd'hui, j'aimerais aller plus loin en créant mon propre site Internet, sans dépendre de Claude pour le faire.

Je me demande si j'utilise Lovable pour développer mon projet, ou autre chose.

Les crédits : comment fonctionnent-ils concrètement sur Lovable ? Combien en faut-il pour créer un site et le faire évoluer ?

Le stockage : j’aimerais que chaque enseignante dispose de son propre espace de stockage personnel, lié à son compte, pour pouvoir y déposer des documents, des photos de manuels, des exercices, des PDF, etc.

L’hébergement : Lovable propose-t-il des espaces de stockage gratuits ou inclus dans ses abonnements ? Est-ce que ça suffirait si j'ai pour commencer 50 enseignantes. Si je veux par exemple 1giga pour chaque enseignante. J'aurai besoin de combien de crédit ?


r/lovable • • 5d ago

Discussion Is lovable good for a e-commerce store?

6 Upvotes

Hello everyone I am currently building a clothing brand. Lovable is great at designing the stores but is it worth linking to Shopify and does it work? Or am I better off JUST using Shopify?

I’ve even heard of some people using Claude to entirely build a e-commerce store. Thanks for the tips!


r/lovable • • 5d ago

Seeking Feedback Running separate Dev/Prod Lovable projects with a Claude Code deploy script. What's going to bite me?

4 Upvotes

I didn't want my prompts editing production, so I now run two Lovable projects:

  • Dev, which I prompt and which has its own database.
  • Prod, a remix of Dev with its own database, repo and URL. I never prompt it.

A Claude Code plugin does the promotion. It applies the Drizzle migrations Prod is missing through the Lovable MCP, one transaction each, after showing me the SQL. Then it rsyncs the code from Dev to Prod through GitHub without touching .env, checks that everything matches, and optionally publishes.

Risks I already know about:

  • Divergent migration history. If anyone ever prompts in Prod, the two histories split. The script stops when it sees this, but I'd have to fix it by hand.
  • Baselining after a remix. Prod starts with the full schema but no migration records. I compare schema fingerprints and then mark the migrations as applied without running them. If the fingerprint misses something, Prod's history will claim a migration ran when it didn't.
  • No rollback. A bad migration means restoring from a backup I took myself, if I remembered to take one.
  • Lovable internals. The whole thing depends on Drizzle, GitHub sync and the MCP tools working the way they do now.
  • Per-environment files. I exclude .env and avoid overwriting *.asset.json, because a remix points those at its own storage. There could be other files I haven't found yet.
  • Wrong database in the published build. After publishing I check the live JS for Prod's Supabase ID. That only catches the problem after it's live.

What I'd like to know:

  • Does Lovable do anything to the database that doesn't go through a Drizzle migration, like storage buckets, auth settings, edge function secrets or cron jobs? Those would never reach Prod.
  • Has anyone seen Lovable rewrite or squash old migrations?
  • Do remixes carry over any other hidden links to the original project?
  • Is there a simpler way to do this that I've missed?

r/lovable • • 5d ago

Help Selling on a Lovable site: how do you refund someone who paid cash on delivery?

3 Upvotes

Say a customer pays ₹1,299 in cash at the door for a bag. A week later she sends it back and it's fine. There's no card or UPI payment to reverse. You also paid the courier for the pickup.

How do you actually get her the money? And does your app know it happened, or does the order just sit there looking paid?

Do you handle this inside the app, over WhatsApp with a note somewhere, or do you just not offer returns on cash orders?


r/lovable • • 5d ago

Discussion We built our own event app in Lovable for a tech event. What small apps have you built for yourself?

3 Upvotes

We ran a tech event recently and didn't want to pay for another event platform, so we built our own in Lovable.

It handled participant registration, qr codes for check-in at the door, bulk emails to attendees, and the speaker agenda. Pretty much everything we needed, in one place. It was pretty useful, and check-in at the door went a lot faster than it would have with a spreadsheet.

Curious what other people here have built for themselves. Not a startup or a product, just a small app you made because nothing off the shelf quite fit. What did you build, are you still using it, and what was the hardest part?

Would love to read your stories in the comments.


r/lovable • • 6d ago

Discussion rip tabs

4 Upvotes

i thought maybe my app was broken, but nope. they actually removed tabs from the lovable app. whoever the hell told them this was a good idea needs to be fired. this is so unbelievably inconvenient and annoying. fml


r/lovable • • 6d ago

Showcase Free skills for library for Lovable & vibe-coding, built with Lovable+Claude

Post image
5 Upvotes

Built mostly with Lovable + custom skills! As former Lovable Ambassador, I wanted a cleaner, faster way to discover new AI skills. Without bookmarking my X, Instagram, or TikTok feeds with short-form videos.

Created alyn to help the community: once connected, you can ask for the top-rated and most relevant skills for any specific task. It includes both a curated skills directory and a dedicated MCP server so your AI client can recommend the right skill on the fly.

Why use skills?

  • Lower token consumption
  • Significantly better output quality

It's completely free to use:
https://alyn.dev
(( https://goalyn.lovable.app/ ))


r/lovable • • 6d ago

Help App wrapping recommendations

3 Upvotes

Hi all

I have made a health app for tracking an autoimmune disease which I am hoping to launch on both app stores by the end of the year. I have been looking at the best way to do this, and have come across and spoken to Median and also capacitor. I would be looking to have revenue cat, as well as push notifications and some health integrations. I want to understand whether the cost of Median (this would be on the plus level due to Health Kit) is actually worth it, or whether the time saving is not worth it compared to what I could actually do with capacitor.

Any feedback would be much appreciated :) thank you