Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Tip-Calculator With CSS Grid, CSS Flexbox, Vanilla Javascript

Larry•190
@ljcutts
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I think I did really good on this project. I had a very hard time trying to put dots inside the zeros and am not sure how to do it. Also, never figured out how to add colors to the dollar images on the right side of the app. This was my first time using Javascript but I feel like maybe I could have had a better solution with that. But out of all of this, the most important I want to know is how to make this compatible with mobile devices(which I know requires media screen with CSS). Any suggestions??

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Zain Mhrez•220
    @ZainMhrez
    Posted over 3 years ago

    Hi Larry, you did nice work. I think the process to calculate the tip and the total bill need some updates: the tip for each person = (bill_value * tip_percent) / people number. the total bill for each person = (bill_value + (bill_value * tip_percent)) / people number.

    I wish this will help you, good luck.

  • Ben•770
    @BenConfig
    Posted over 3 years ago

    The 'dots inside the zeros' are a feature of the Space Mono font family. It looks like you are using the Roboto font family which does not have the dots.

    Why not just use the character '$' and then you can apply the color property?

    You should try building the page for mobile first. The mobile design is usually much simpler than the desktop design so it makes sense to start with that. You then apply media queries when you have more viewport space to work with.

  • Nakoya Wilson•1,530
    @nakoyawilson
    Posted over 3 years ago

    The dots in the zeros are from the Space Mono font. Your import line for the Space Mono font is currently incomplete so it's not being imported properly. If you use the following import and change your ff-primary and ff-secondary to 'Space Mono', monospace; the Space Mono font should work properly on your page.

    @import url("https://fonts.googleapis.com/css2?family=Space+Mono:wght@400;700&display=swap");
    

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

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