Cursor is an AI-powered code editor designed to help developers in writing, debugging, and optimizing code.
Declaring that it was made for both novice and experienced developers, we wanted to test how well it actually works for different types of users. In our analysis, we tested getting started with Cursor, how helpful AI suggestions are, and whether it is an intuitive experience.
1. Make it easier to understand onboarding
2. Fewer usability errors and hesitations
3. Make it faster to create a new project
BEFORE
AFTER
- No feature descriptions or explanation
- Little to no buttons to start new projects Difficult to
- understand for novice developers
- Descriptions of each feature
- Buttons to navigate starting a new project, learning the interface, learning to code
- Descriptions for each new page when selected
“It’s hard to read. But you know what will help? Let’s say I click on it and then this search window. If it pops right on top of this one. Then I know like you click on it and there’s another screen opens where you search.”
“I would have liked if before I signed up, if there was just something telling me what Cursor was a little bit more.”
“Yeah, I Definitely think adding these three buttons will benefit like beginners or people who are not very familiar with VS code who just want to start live coding.”
We learned how important it is to design onboarding especially more intuitively, with clarity, and with different experience levels and accessibility in mind.
We realized that even small changes like instruction or clearer buttons can ease hesitation for users.
If we had more time, we would’ve tested with an even wider range of users, including complete beginners, and incorporated accessibility needs earlier in the design. Moving forward, we plan to explore more personalized onboarding options, stronger support features like FAQs, and long-term testing to see how the experience holds up over time.