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

html css grid flexbox scss Javascript Mobile firts

bem, sass/scss
P
RF13•610
@rf1303
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?

*It was a challenge to keep the interface intuitive and functional at the same time, but I learned a lot about best practices with JavaScript, event handling, and CSS styling. If I had to do it over again, I would spend more time up front planning the code structure and modularizing features to make them more reusable and maintainable. I would also try to implement more extensive testing to ensure the form's robustness to all kinds of user input.

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

One of the main challenges was to correctly handle the validation of numeric input, in particular to avoid invalid input such as letters or null values, and to ensure that the calculation was only performed if all fields were valid. It was also difficult to determine when to show or hide error messages without affecting the user experience. To overcome this, I used addEventListeners on events such as input, keydown, and blur to control the state of each field in real time. I also used conditional validations to provide clear visual feedback. Breaking the logic into reusable functions helped me keep the code more organized and easier to debug.

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

**In particular, I would like help optimizing the validation of numeric input, as it works but could be simplified or better structured according to best practices. I am also interested in improving accessibility and user experience when displaying errors and visual messages, especially on mobile devices. Also, any advice on how to better organize JavaScript code and separate responsibilities between HTML, CSS and JS would be very helpful to scale the project in the future.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ethan John Paguntalan•260
    @dev-ethanjohn
    Posted 3 months ago

    Hi, we couldn't preview the live site. Please try to update your demo site. Thanks!

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