[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  Cody Schneider [@codyschneiderxx](/creator/twitter/codyschneiderxx) on x 45.9K followers Created: 2025-07-26 20:11:49 UTC eingineers are in this ecochamber of no one using lovable and its easy to say this when you're not talking to normies and yeah lovable probably has a ton of transitory revenue but their "aha" moment is insane when it one shots a thing and the reason people are churning is because setting up DB, auth, payment, and email is hard after you built the killer feature EG most people start with the product, and then try to implement DB auth stripe auth and email after and lovable has trouble with this but this is easily solved with forced boilerplate out of the box, for every product lovable should have DB auth payment and email locked in they need to be opinionated about this this creates a skeleton that a user can then flesh out and if you can build an app with: - X killer feature - DB - Auth - Payment - Email anyone can get paying users, meaning they won't churn  XXXXX engagements  [Post Link](https://x.com/codyschneiderxx/status/1949201007625511374)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
Cody Schneider @codyschneiderxx on x 45.9K followers
Created: 2025-07-26 20:11:49 UTC
eingineers are in this ecochamber of no one using lovable
and its easy to say this when you're not talking to normies
and yeah lovable probably has a ton of transitory revenue
but their "aha" moment is insane when it one shots a thing
and the reason people are churning is because setting up DB, auth, payment, and email is hard after you built the killer feature
EG most people start with the product, and then try to implement DB auth stripe auth and email after
and lovable has trouble with this
but this is easily solved with forced boilerplate
out of the box, for every product lovable should have DB auth payment and email locked in
they need to be opinionated about this
this creates a skeleton that a user can then flesh out
and if you can build an app with:
anyone can get paying users, meaning they won't churn
XXXXX engagements
/post/tweet::1949201007625511374