Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

tip-calculator-app-main

Mudasir Nadeem•430
@mudasirNadeem
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?

I’m most proud of the responsiveness and clean structure of the project. I approached the design with a mobile-first mindset, which allowed me to ensure that the user experience is optimized for all devices. The use of CSS Flexbox helped me maintain flexibility in the layout, and I successfully incorporated JavaScript logic to manage dynamic content and calculations, like percentage formulas.

Next time, I would focus on improving the accessibility of the project by adding ARIA labels and enhancing keyboard navigation. Additionally, I plan to explore CSS Grid more deeply to see how it can complement Flexbox in creating more complex layouts.

This reflects both your achievements and a plan for future growth. Let me know if you'd like any changes!

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

One of the main challenges I encountered was ensuring the accuracy of calculations when dealing with percentages and dynamic user inputs. It was tricky to get the right formula to handle both tip calculations and total bill splits across multiple people. I resolved this by refining my understanding of JavaScript number handling, utilizing functions like parseFloat() and toFixed() to ensure the results were accurate and displayed correctly.

Another challenge was ensuring the project remained fully responsive across various screen sizes. By adopting a mobile-first approach and utilizing CSS Flexbox, I was able to overcome layout issues. Through continuous testing and adjusting breakpoints, I ensured the design worked seamlessly on different devices.

This highlights the obstacles you faced and how you tackled them, showing growth and problem-solving skills. Let me know if you'd like to add or modify anything!

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

I would appreciate feedback on the accessibility of my project. While I focused on responsiveness and clean UI design, I want to ensure the website is accessible to all users, including those using screen readers or keyboard navigation. Specifically, I’m looking for advice on implementing ARIA attributes and any improvements I could make to the overall semantic structure of the HTML.

Additionally, I’d like input on how to better optimize my JavaScript code, particularly for handling dynamic data and user inputs more efficiently. I’m also exploring CSS Grid to complement the Flexbox layout and would love any suggestions on improving my approach in areas where Grid might be more appropriate.

This gives the community a clear direction on where they can help, leading to more valuable and specific feedback. Let me know if you'd like any adjustment

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriverion•220
    @Adriverion
    Posted 10 months ago

    excelente solución

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

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.

Oops! 😬

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

Log in with GitHub