LeetCode User Reviews

Customer Experience

Positive experience50.0% of reviews
Neutral35.0% of reviews
Negative experience15.0% of reviews

~ Based on 40 written reviews from the US App Store.

Is LeetCode Safe?

LeetCode appears safe based on user ratings. AppsHunter Safety Score for LeetCode is 95/100.

This assessment is based on 439 user ratings, with an App Store average of 4.8/5.

Safety Analysis

94.1% of ratings point to a safe experience
2.7% of ratings suggest some concerns
3.2% of ratings point to a risky experience

~ Based on 439 App Store ratings for LeetCode.

Is LeetCode Legit?

LeetCode has limited verification signals. AppsHunter Legitimacy Score for LeetCode is 53/100.

Based on 53 of 100 points across 7 verification signals from App Store and developer data.

Top reviews

Great work!!

Nice App!

Think big code big

I downloaded the app on my phone just to keep a track and it got automatically installed on my macbook , on my mac too its giving me fantastic experience, i am literally amazed , for now i just want one improvement in this existing app , add a feature so that we can access the recent submissions, while going to sleep we can just open the code and see it , its helpful in revision.
Show more

Good Start

I like being able to solve some DSnA on the go but not having error reports or know what the test case that failed was is extremely frustrating.

An issue

There is an issue with email verification

Good stuff

Even tho it made for iPad this has better ui and does the job so it is good the only thing I will tell the dev to add is the leet ask in this aswell rest everything is awesome

Finally!!

I have been waiting for this app for years!! I always play puzzles on my phone to pass time and wished I could play Leetcode so I can feel less like I’m wasting my time. This is perfect!! THANK YOU.

Leetcode App Review

Much Needed App for Leetcode, Glad it came.

Poor devx

1. Error message is not displayed when a test case fails, making it difficult to identify the reason for the failure.
2. Failed test cases cannot be accessed or viewed after execution.
3. Special symbols are not available on iPad and should be supported.

Cannot see runtime errors

Broken ui when submitting

Waste of money

Honestly, after leetcoding for two years, and trying to get the most from solving problems and the education side, it’s just not as useful as it used to be. The app itself is barebones and you cannot maximize the whole subscription you pay for on the app. In addition, the problems are great to learn from but again now with AI you can use other tools to increase your programming knowledge. Leetcode is trash now. Not worth paying for it especially when you need to pay more for other modules as the pay off is very slim given the sector and not worth the price at all. The app again is very poor as you cannot even use the education portion even when paying. Just use AI to study the problems or build a program application and save yourself the time and money by not using this app or supporting leetcode. Also, their support team is very poor in customer support just beware when bringing up issues to them or improvement features.
Show more

Brilliant, but with issues

There’s a few bugs. For instance, on my iPhone 11 (iOS 18), when I run a test and it fails, it just says “runtime error” or “syntax error” with no additional information.

Also, the new keyboard while innovative, has some visual glitches on my phone, especially when hiding it and re-opening it.

Nice ux

Way better than doing it in mobile browser

Runtime errors is not visible

Hi LeetCode Team,

Thank you for providing this app. It has been extremely helpful for practicing coding problems and improving problem-solving skills. I appreciate the effort that has gone into making learning and interview preparation more accessible.

I would like to share a few suggestions that could significantly improve the user experience:

1. Runtime Error Visibility
Currently, when a runtime error occurs, it is very difficult to identify exactly where the error happened and what needs to be fixed. Detailed runtime error messages, including the line number and error description, should be clearly displayed. This issue seems to affect both Python submissions and Database (SQL) queries.
2. Expected vs Actual Output Table View
For database problems, there should be a clear table view showing the Expected Output and Actual Output side by side, similar to the browser experience on the LeetCode website. This makes debugging query results much easier.
3. Consistent Experience Across Devices
The table view available in the browser experience should also be visible in the macOS application and on iPad. Currently, the lack of proper tabular output makes it difficult to compare results and understand mistakes efficiently.

These improvements would greatly enhance the debugging experience and make learning more effective across all platforms.

Thank you again for building such a valuable learning platform. I look forward to future updates and improvements.

Best regards
Show more

Good but needs more features

Doesn’t have submission history or recent accepted solutions. Much needed to resume work from laptop.

PLEASE ADD DISCUSSIONS

Long been waiting for an app which is nice. But it is not clear if discussions for problems exist on leetcode app, PLEASE add discussions. Discussions was a major joy in solving the problem because I got to see other people struggle with me, give hints, or feel like I was part of a community. PLEASE ADD DISCUSSIONS FOR THE PROBLEMS!!
Show more

Good user experience

I can keep up with daily practice using this app. Thanks

Great UI

Amazing app to do Leetcode on the go.

Accessibility issues for voiceover users

This application is very good, but it has many accessibility issues such as unlable buttons so kindly make it accessible so that blind can also use it

Loading too slow

The homepage and profile data is taking around 15s to display

Editor

When typing code in editorials when we click left ( right is not coming automatically but in website it comes same for { same for curly bracket please fix it