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

Simple Password Generator App using HTML, Sass, BEM and JavaScript

P
Schindler Dumagat•340
@schindlerdumagat
A solution to the Password generator 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?

By building this project, I practiced using AI to solve problems. For me to become an efficient and effective developer, I need to learn how to use AI properly. I need to understand the code provided by AI before implementing in my solution. In need to learn how to prompt AI effectively to give me more accurate responses. I shouldn't be reliant on AI too much and just copy pasting code without understanding and forget about searching solutions on the internet and reading documentations.

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

The most difficult challenge that I have encountered is how I can override the default styling of the slider and the checkbox to match the design. To overcome this problem, I used ChatGPT to ask for some ways on how to do this. It gave me some sample code and I modified it to my own needs.

I also asked AI to give me some sample code on how I can generate a password based on some selected options and evaluate its strength. I implemented it in my solution but made sure to understand the code provided.

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

Here are some of my concerns:

  • My password generation algorithm is simple and I wanted to asked for a better algorithm.

  • My password evaluation algorithm is simple and I wanted to asked for a better algorithm. It seems like my password evaluation is not accurate enough.

Any feedback is also welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Mehmet Çağrı Ekici•330
    @mehmetcagriekici
    Posted 8 days ago

    Congratulations, great effort! I have few feedbacks, first of all I think you need more comments to explain your code, this is crucial for other developers to understand your work, and for readability. You have a clean HTML structure, I just don't understand why you created SVGs instead of using provided images that came with the starter files. As for your JavaScript, you don't need to hardcode character sets, you can use the ASCII table. Otherwise, clean organized file. I know so little SASS, so I can't say anything about it. But your site looks fine, it's responsible, so it can't be bad.

    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