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

Tip calculator app

Bunchydo•570
@Bunchydo
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?

Proud of:

Successfully handling decimal input in number fields by removing spin buttons using step="any". Aligning images within containers using position: relative and position: absolute, and centering them with transform: translateY(-50%). Organizing global styles (fonts, colors) first to set up the foundation before focusing on layout. Effectively managing hover states with CSS selectors like :not(:last-child) to simplify the styling process without adding extra divs. What I’d Do Differently:

Instead of relying on JavaScript for some layout adjustments, I’d explore more CSS-based solutions like flexbox or grid to handle responsiveness and dynamic content changes. I would work on optimizing media queries to ensure they target all screen sizes efficiently. Focus on testing the app on multiple screen sizes and devices to refine the layout before finalizing styles.

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

Challenges:

Getting input fields to accept decimal values without the spin buttons was tricky. The step="any" attribute was a new concept, but after some testing, I found it works well for number inputs. Handling vertical centering using top: 50% and transform: translateY(-50%) was initially confusing. I had to learn the relationship between the element’s height and container height to make it work properly. Some CSS properties like height: 100% didn’t behave as expected due to nested percentage-based heights, so I had to adjust my approach and sometimes use height: auto for better results. Solutions:

Used step="any" on number inputs to allow decimal values. Used position: relative on parent containers and position: absolute for child elements to fine-tune image alignment. Experimented with height: auto in some cases where 100% was causing layout issues.

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

CSS Grid and Flexbox: I would appreciate advice on how to improve the responsiveness of my layout using CSS Grid and Flexbox. I’m currently using a lot of height: 100% and flex properties, but I would like to make the design more adaptive to various screen sizes.

JavaScript Calculations: I’m handling some dynamic calculations in JavaScript (e.g., calculating tip amounts). I’d love feedback on how to optimize these calculations or make the interaction smoother (e.g., avoiding issues when values are updated rapidly).

Media Queries: I need some suggestions for structuring my media queries to ensure the app works well across different devices and screen sizes. Any advice on best practices for mobile-first design and handling breakpoints would be helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • abdulrrahmann•270
    @abdulrrahmann
    Posted 5 months ago

    great job! your solution is amazing. you can take a look at mdn web docs https://developer.mozilla.org/en-US/docs/Web/CSS/grid the grid and flexbox are explained in depth.

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.

Oops! 😬

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

Log in with GitHub