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

React QR Code Generator

react, accessibility
Travolgi 🍕•31,320
@denielden
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there :)

This challenge was to build the QR Code component, but it has become something more complex than a simple component!

Inspired by another project, I wanted to add features to this challenge using React:

  • On load, it shows the default basic QR Code
  • Added a form that allows the user to enter a website URL to generate a QR Code for it
  • Dynamically update the QR Code as you type the URL
  • Dynamically update the color and background of the QR Code based on the customization input entered by the user
  • When the form is sent, the .png of the generated QR Code is downloaded

I am eager to further evolve this project and learn much more connecting a serveless database! For now I'd be happy to have some feedback ;)

Special thanks to @Remus432, he have really inspired me to create this dinamic component!

Thank you for taking the time to check out my project! And Happy coding ;)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel•140
    @obriedan
    Posted over 3 years ago

    Amazing work! What library did you use to generate the QR code?

    Your form validation could use some extra information, it requests a URL, but doesn't specify that you need the protocol. www.google.com does not work, but https://www.google.com does. 👍

    Love it either way. Super clean.

    Marked as helpful
  • Kamasah-Dickson•5,570
    @Kamasah-Dickson
    Posted over 3 years ago

    Your solution is really good but I think there is supposed to be a restriction for the user to not choose same color for the QR and the card . E.g choosing red for the QR and red for the card background overlays the QR. Besides

    your solution is so inspiring :)

    Marked as helpful
  • ViicDev ☪︎•370
    @ViicDev
    Posted about 3 years ago

    excellent work 🤯

  • Mohit Jaiswal•90
    @mohit421
    Posted about 3 years ago

    Great, this really inspire me, this challenge at different level.

  • Martin•540
    @nonso01
    Posted over 3 years ago

    ooo! my gosh 😂😂😂! this is just mind blowing! great work sir

  • Rizkyani Indah Lestari•40
    @rzkyndhlstr
    Posted over 3 years ago

    wow!!!! so amazing👍👍👍👍👍

  • Nathanael Bonfim•10
    @nathabonfim59
    Posted over 3 years ago

    Awesome! Really liked that you provided a way to download the generated QR Code.

    Definitely something I'm looking forward to implementing in my own project, in a future iteration.

  • Nícolas Gabriel•140
    @Nick-Gabe
    Posted over 3 years ago

    Im really impressed with your result, you surely took the challenge even further. 👏👏

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.

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

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

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