Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 19 days ago

Responsive Tip Calculator App using Sass and JavaScript

P
Schindler Dumagat•310
@schindlerdumagat
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 was able to practice my code organization skills in this challenge. I read about the 7 - 1 architecture of Sass and made an inspiration out of it to organize my Sass files. I practiced creating comments and functions to separate my logic in my JavaScript file and make my code more understandable. I refactor my code until I am satisfied with it. I use AI tools like ChatGPT to help me in my learnings and in building this project without copy and pasting code.

Next time, I will use AI more often to get feedback for my code and get better each day.

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

One of the challenges that I have encountered is how I can organize my styling for better readability and maintainability. To overcome this, I read same articles and documentations and watch a few videos about it. I even asked AI for some help with this challenge and I refactored my code a few times. After doing all of these, I was able to write the code that I am proud of.

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

Here are some of my concerns:

  • Is my JavaScript code easy to understand? I created a lot of functions in order to separate the logic and make it more readable. Hopefully, I was able to achieve that.

  • Is my Sass files organization easy to follow? It is my first time using an architecture in organizing my Sass files. I got inspiration from the 7 - 1 architecture by Sass and change it a little bit for my project.

  • Did I use the correct HTML elements for this project? I used a radio group and radio role for the tip percentage selection. I asked AI about it and it seems appropriate for me.

  • How can I improve the accessibility of this project? I used a couple of aria attributes but I don't know if I used it correctly. Just correct me if I am wrong.

  • How is the user experience of my output? I wrote a lot of logic in my code and I want you to try out my solution.

As usual, any feedback is welcome and I will be happy to read it.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Schindler Dumagat's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.