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

Tip Calculator App

P
Jan Kotvaš•460
@DrakeHermit
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 learned a ton working on this challenge, and I really tested my knowledge with applying either submit or reset state based on the situation. Is it a perfect solution not by a long shot, but I am actually proud of myself for being able to make it work the way I wanted it to work. I also learned that by writing CSS poorly you will end up with a lot of !important statements, but that is something I'm going to keep an eye on in the next challenges I work on. CSS wise even though it's not perfect it looks decently good.

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

I encountered quite a bit of challenges considering the fact this was my first time working on such a challenge. But I overcame all the obstacles by either googling what I didn't know or by asking chatgpt a general question that would then lead me to the correct solution. I never ask chatgpt to solve a problem for me because that is definitely not a way to learn.

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

I would love if someone reviewed my code, not just JS though. I am doing my best but I know for a fact that there are a lot of features I am not aware of that can help me out structure my code better.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,790
    @danielmrz-dev
    Posted 12 months ago

    Hello @DrakeHermit!

    Your solution looks excellent!

    I have just one suggestion:

    📌 Make sure you add min-height: 100vh and justify-content: center to the body to place the card in the middle of the page. Like this:

    body {
        min-height: 100vh; /*  Add this line ✅  */
        display: flex;
        flex-direction: column; /*  Add this line ✅  */
        justify-content: center;
        align-items: center;
        background-color: var(--light-grayish-cyan);
        font-family: 'Space Mono', sans-serif;
    }
    

    I hope it helps!

    Other than that, great job!

    Marked as helpful

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