As mentioned last week, Dan built his app entirely through Cursor AI. I wanted to learn more about that experience and how a non-coder would navigate and use Cursor.
Here are 14 takeaways from our chat.
(Apologies for lack of organization. I wanted to get this out sooner)
1. Cursor has come a long way since I explored it months ago.
2. It can create files in your Xcode project.
3. You can run the iOS simulator from Cursor.
4. You can compile the project in Cursor.
5. Build errors show up in Cursor which makes it easier to as Cursor to address them.
6. The AI can get caught in loops. You have to be able to identify when this is happening.
7. The AI can sound confident and provide a solution, even when it has no idea what to do. So it’s solutions will not always work.
8. You need to keep backups in case it messes the project up.
9. There is a versioning system built into Cursor.
10. A non-coder won’t know how to architect the app for easy maintainability (and Cursor won’t automatically do it).
11. The solution that the AI applies may break/modify previous features that have been working.
12. You have to explicitly reduce its scope so that it doesn’t modify code that you don’t want it to touch.
13. Because of this, it’s better to build the app in rough, broad strokes and then refining linearly.
14. If you know Swift/SwiftUI, using Cursor will be much much better
This is probably me stepping into a pitfall, but while my team is building the home reno AI app, I’m going to start my own personal indie app with Cursor.
I want to explore Cursor myself and this way, we’ll get 2 apps released instead of 1.
... Or maybe we'll end up with 2 unfinished projects instead 😂
CodeWithChris
As mentioned last week, Dan built his app entirely through Cursor AI. I wanted to learn more about that experience and how a non-coder would navigate and use Cursor.
Here are 14 takeaways from our chat.
(Apologies for lack of organization. I wanted to get this out sooner)
1. Cursor has come a long way since I explored it months ago.
2. It can create files in your Xcode project.
3. You can run the iOS simulator from Cursor.
4. You can compile the project in Cursor.
5. Build errors show up in Cursor which makes it easier to as Cursor to address them.
6. The AI can get caught in loops. You have to be able to identify when this is happening.
7. The AI can sound confident and provide a solution, even when it has no idea what to do. So it’s solutions will not always work.
8. You need to keep backups in case it messes the project up.
9. There is a versioning system built into Cursor.
10. A non-coder won’t know how to architect the app for easy maintainability (and Cursor won’t automatically do it).
11. The solution that the AI applies may break/modify previous features that have been working.
12. You have to explicitly reduce its scope so that it doesn’t modify code that you don’t want it to touch.
13. Because of this, it’s better to build the app in rough, broad strokes and then refining linearly.
14. If you know Swift/SwiftUI, using Cursor will be much much better
This is probably me stepping into a pitfall, but while my team is building the home reno AI app, I’m going to start my own personal indie app with Cursor.
I want to explore Cursor myself and this way, we’ll get 2 apps released instead of 1.
... Or maybe we'll end up with 2 unfinished projects instead 😂
1 month ago | [YT] | 28