Subscribe
Sign in
Hi cursor users!
Personally I started creating app on cursor Just for fun, but recently I started to understand basics and my apps started to become more marketable. What about you? How is going your vibe journey?
Hello, PH!
I m a designer who boldly switched from Framer, which I had been loyal to for two years, to Cursor recently. This has been the best decision I ve made this year. The biggest reason is that the cost savings have been truly dramatic.
Cost comparison:
Framer:
Even the mini version costs $15 per month ($180 annually), and running 3 sites would cost $540 a year (if I had created with Framer, it would have added another $180, totaling $720).
Cursor:
Just $120 for an annual subscription! Unlimited projects possible. And there are no hidden costs or additional feature fees at all. The Cursor subscription fee covers everything. (I feel like I m advertising now;;;)
Besides the cost, here are the other benefits of Cursor for designers:
- Anything is possible beyond the features offered by Framer.
- No need for complicated tutorials or studying; you can use it right away.
- You can implement everything you imagine just with prompts.
I think I ll continue using Cursor, so I d love to connect with other designers. Is there a group for designers using Cursor?? I want to share good tips with designers who use Cursor!
At @Bucket, we're always looking for products that can boost productivity and inspire us to build better software. We recently experimented with @Cursor to replace @Github Copilot.
Key takeaways
Tab completion: Cursor includes a helpful tab completion feature, suggesting refactorings and improvements as you go huge time saver!
Chat: the chat/composer is better than Copilot as it can modify across files in the codebase. However, we still needed to correct the code most of the time :/
Full context: Cursor has full context, so it provides more helpful advice and changes
Generating comments: it makes it easier to add code comments they need clarifications from time to time tho
Working with existing codebases: Cursor seems better at writing code from scratch than contributing to large existing codebases
Hallucinations: as far as we can tell, it had fewer hallucinations compared to alternatives
Prompting strategies: being somewhat specific in prompts by referencing classes and functions seems to work well We're currently experimenting with `.cursorrules` files to improve prompt quality
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X:
"1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
Hello PH!
I'm Hyuntak form South Korea, quite new to this community, first time posting.
I'm a med student and solo developer.
