👉🏼 Apply to join the Early AI-dopters Community: bit.ly/3ZMWJIb 📅 Book a Meeting with Our Team: bit.ly/3Ml5AKW 🌐 Visit My Agency Website: bit.ly/4cD9jhG
Man, u cant release this at this hour, ive got work in the morning. Now i have to look at this. :D Thnks for the pace and explaination in your videos. Suits me like a glove. Take care
Mark, this is SO awesome. Thanks so much for showing these tips. I love the idea of a place you can go to get design ideas and feed them into Lovable instead of having to spend so much time back and forth until you create just what you want. I was wondering if you have any advice for code regression. I find that I get something just the way I want it and while working on another part of the app Lovable breaks things I had working or changes it in ways that I didn't want.
thank you so much! Always a pleasure. My biggest tips for code regression related issues are the following: 1) As you'll (hopefully) see from my examples, I do my best to separate UI from functionality. I ladder my way down from shell, to prettier shell, to drafting the functional components without the functionality, to then diving into the technical components. Ideally, you start building the technical components one thematic type at a time (e.g. build the ability for the LLM to process input data, then build the ability to properly parse said data into markdown) to offer you ample checkpoints to rollback to should you need to. 2) The more you commit to GitHub, the better you'll be able to manage your versioning. Github will store all your commits that you can manage and re-import. Every change you make and push to the repository will be automatically reflected in Lovable and vice versa.
Great video Mark. I am starting off with Lovable but do you think it's possible to build and launch a fully functional MVP using Lovable without having any developer skills or being an expert in React or Python.
Thank you Dan! I think as long as the word ‘MVP’ is in your goal, it’s completely viable to use it. Depending on the complexity of your application, I would be hyper-intentional to map out all the functionality you’re looking for, the ideal design that drives your inspiration, and implement from the shell to the easiest functionality first. Leave the meatier parts till later so that you can easily rollback to a stable version of the application.
Is there a reason you didn't build a full landing page from Figma to Lovable? Can Lovable not handle that? And regarding 21st dev, why not just copy paste code examples (from any number of UI Component Libraries) directly into your project pages. Why prompt Lovable to build it at that stage. I can see using lovable to iterate afterwards, but seems like a wasted step, with wasted time and resources.
1. No particular reason, just wanted to show the functionality. 2. Some of the code examples are too long for the context window, so the prompt helps get around that limitation. 3. Building the shell is much easier at the beginning than after adding tons of functionalities. This seems to be the case with bolt and lovable.
👉🏼 Apply to join the Early AI-dopters Community: bit.ly/3ZMWJIb
📅 Book a Meeting with Our Team: bit.ly/3Ml5AKW
🌐 Visit My Agency Website: bit.ly/4cD9jhG
Thanks Mark. This was fantastic. I learned so much from this. Eve using Figma was an eye opener. Who new!!
So happy to hear Kenneth; these things are changing by the day, so I'll make sure to stay on top of it for you!
This is very helpful, thank you so much 🙏♥
So happy to hear that! 🦾🦾
Bro this is pure gold!❤
so happy you found it helpful!
Very useful tips! Thanks very much.
My pleasure Pierre!
I love it! You make me stay on top of things…
Just wait for my next video 🫡
Great content - as always I appreciate the depth of coverage in your videos!
My pleasure Eric! Always listening to my best viewers’ feedback 😅
Thanks Mark, great content, as always
Thanks Dimitri! Appreciate you 🦾
Man, u cant release this at this hour, ive got work in the morning. Now i have to look at this. :D
Thnks for the pace and explaination in your videos. Suits me like a glove.
Take care
hahaha my pleasure Martin!
I love my long form videos.
Mark, this is SO awesome. Thanks so much for showing these tips. I love the idea of a place you can go to get design ideas and feed them into Lovable instead of having to spend so much time back and forth until you create just what you want. I was wondering if you have any advice for code regression. I find that I get something just the way I want it and while working on another part of the app Lovable breaks things I had working or changes it in ways that I didn't want.
thank you so much! Always a pleasure.
My biggest tips for code regression related issues are the following:
1) As you'll (hopefully) see from my examples, I do my best to separate UI from functionality. I ladder my way down from shell, to prettier shell, to drafting the functional components without the functionality, to then diving into the technical components.
Ideally, you start building the technical components one thematic type at a time (e.g. build the ability for the LLM to process input data, then build the ability to properly parse said data into markdown) to offer you ample checkpoints to rollback to should you need to.
2) The more you commit to GitHub, the better you'll be able to manage your versioning.
Github will store all your commits that you can manage and re-import.
Every change you make and push to the repository will be automatically reflected in Lovable and vice versa.
Super helpful thanks so much. Would love to see more Like these
Pumped it was helpful!
Definitely going to make more
Great video Mark. I am starting off with Lovable but do you think it's possible to build and launch a fully functional MVP using Lovable without having any developer skills or being an expert in React or Python.
Thank you Dan!
I think as long as the word ‘MVP’ is in your goal, it’s completely viable to use it.
Depending on the complexity of your application, I would be hyper-intentional to map out all the functionality you’re looking for, the ideal design that drives your inspiration, and implement from the shell to the easiest functionality first.
Leave the meatier parts till later so that you can easily rollback to a stable version of the application.
This is definitely possible
❤❤
how can i connect with you ?! ❤
hey! What are you looking for specifically?
@Mark_Kashef Collaboration !!
Anybody know the timestamp where pricing is mentioned? Or is using the plugin free?
There wasn’t a fee attached to it when I integrated it
Is there a reason you didn't build a full landing page from Figma to Lovable? Can Lovable not handle that? And regarding 21st dev, why not just copy paste code examples (from any number of UI Component Libraries) directly into your project pages. Why prompt Lovable to build it at that stage. I can see using lovable to iterate afterwards, but seems like a wasted step, with wasted time and resources.
1. No particular reason, just wanted to show the functionality.
2. Some of the code examples are too long for the context window, so the prompt helps get around that limitation.
3. Building the shell is much easier at the beginning than after adding tons of functionalities. This seems to be the case with bolt and lovable.