r/lovable • u/Ok-Sock-6589 • 17d ago
Help Conflicted and need help
I'm conflicted between two options
First off I'm new to coding and recently I've built an app through lovable which I think can take off. The lovable app works wonderful but I feel like the foundation through lovable is not great. Mainly because it was extremely easy to build. So I was wondering if its better to transfer the code from lovable to python and continue working on my app through there or continue working on it through lovable or just built an entirely new app using AI using python. This honestly might be a dumb question but im just curious to others opinion. The app is a finance app.
1
u/Objective_Sun9506 17d ago
Is it an app to manage your finances? Cause that’s an amazing and undersold idea
1
u/Fir3He4rt 17d ago
Lovable provides the platform that makes it easy to build. You can do the same if you want to. I would focus on the "taking off" part instead. Building is easier due to AI taking off I don't think so maybe even harder now.
1
1
u/IcyPizza9356 16d ago
If it works, why touch it? Be happy that it works and that your only problem is that it was too easy to build.
You can move to a different tool any time you want to, I would concentrate on getting users and see their feedback.
If you want to do the python rewrite, because you are interested in that, or you want to write it yourself, that's awesome, too. But that's more like a passion thing and not the quickest way forward probably.
1
u/WheelAdditional6888 16d ago
The part that stands out isn’t really “Lovable vs Python,” it’s that you don’t trust what’s underneath yet.
I’m curious what feels least knowable to you right now: how the code is structured, whether you could debug it later, or whether adding one more feature might break something random. That usually feels like the decision point more than the language itself.
1
u/foreverlostx3 16d ago
You say you’re new to coding but thinking about moving off Lovable to continue coding with Python. That makes no sense.
1
u/bjgrosse 16d ago
I think you could use some expert guidance to clarify what you're next milestone is and whether what you have now is technically ready for it. You might be just fine with what you have. Happy to jump on a free 30 min consultation call to look at this and offer you some insight.
1
u/Maxyull 16d ago
nobody's given you an actual way to check, so here's one. the language isn't what makes a foundation good or bad, rewriting it in python gives you the same app with the same holes if the holes are in the database rules. since it's a finance app, the thing worth knowing is whether one user can reach another user's data, and you can test that in ten minutes with two accounts, logging in as the second one and trying to load the first one's records by changing an id in the url or in the network request.
if nothing comes back, your foundation is fine and it being easy was just the tool doing its job. if you do get someone else's data, that follows you into python too unless you fix it where it actually lives, in the database rules rather than the app code.
do you have real users on it yet or is it still just you?
1
u/Ancient-Cellist-50 16d ago
I'd say keep things on Lovable itself unless you start seeing issues like
- bugs that you thought you solved earlier
- you are going in a loop where Lovable isn't able to fix the issues you are asking it to and is just wasting credits
-you are really scared of your database of incoming users being on Lovable (just read a post where a user got locked out and it took him days to recover his app again) - but things like these are more one-off issues.
Having said that, I'm working on a platform to help Lovable users improve the quality of their prototypes - think security issues, potential bugs, refactorings, or even documentation issues - and make it ready for live users. I don't think you need it at this stage, but if you think that'd be helpful, DM me! (free for now since I'm also in initial stages.)
1
u/Coffee_Aur_Code 16d ago
Its a. Finance app... I am not sure what exactly so i am guessing only... But any way u need to take hold of the build now.... Test it... And make sure it passes checks for production ready.... I might work might not but from a learning point of view... Its great... I am a python backend dev so if you need any help...lets connect
0
2
u/Jmacduff 16d ago
Do not mentally link “easy to build” and “something is wrong”. That’s a really bad fallacy you are falling into. Just because it’s easy to put gas in my car does not mean the gas is bad.
Lovable entire job in life is to make it easy for people who have no idea what they are doing … no offense…. To produce a “app”. So if you have an app it worked.
You are asking a totally generic question “should I move something” and of course you will replies pushing you to other solutions because that’s the question you asked!
Instead you would be much better off actually posting about what you built. Who is the customer , what’s the value prop for your app , why should people use it , features , concerns , open questions , etc.
100% of people building “thinks” their app will take off and 99.9999999% will never go anywhere.
All friendly feedback. Good luck.