Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 23 days ago

Tip Calculator App Built with React, Zustand & Tailwind

jest, shadcn, zustand, react
Arash Asghari•220
@AriArash44
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

One of the highlights of this project was utilizing Zustand for state management. Compared to Redux and React's Context API, I found it simpler, more intuitive, and easier to work with.

Additionally, working with Jest and a TDD approach (Red-Green-Refactor) was insightful—even for a simple function, it demonstrated how test-driven development helps in handling edge cases effectively.

I also enjoyed using ShadCN. It accelerated development, provided complete access to the source code, and offered a solid set of UI components. However, for simpler components like buttons and inputs, it felt a bit unnecessary, with too many extra class names. I’d prefer to use it in more complex components like carousels or accordions.

For my next project, I’ll focus more on accessibility improvements and exploring Next.js, ensuring the app is both performant and user-friendly.

What challenges did you encounter, and how did you overcome them?

One of the biggest challenges was modifying ShadCN’s default UI. The extensive predefined classes made customization harder than expected. Additionally, its theme system felt overwhelming, automatically defining colors that I didn't prefer, leading me to remove the default theme entirely.

This experience made me question whether ShadCN was the best choice for this particular project. However, as an exercise, it was valuable in understanding its strengths and limitations. Moving forward, I’ll use ShadCN selectively, reserving it for more complex components instead of basic ones.

What specific areas of your project would you like help with?

I’m open to any suggestions regarding architecture, best practices, UI improvements, or optimization.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Arash Asghari's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.