Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Created by using React ⚛️, Fetch API 🌐, Styled Components 💅, SCSS 🎨

animation, fetch, react
svyatoslavkk•90
@svyatoslavkk
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


📁 Project: Advice Generator

🔗 GitHub Repository: https://github.com/svyatoslavkk/advice-generator-app-main

🧰 Tools and Techniques:

React ⚛️ Fetch API 🌐 Styled Components 💅 SCSS 🎨 Responsive Design 📱 Animation 🚀 Git (Version Control) 🐙 Deployment on Netlify ☁️ 💡 Summary:

I created an advice generator app that provides users with random advice. It's responsive and visually appealing. Users can click the dice icon to get advice, and the count increases with each new advice.

👉 Live Demo: https://advice-generator-app-main-one-alpha.vercel.app/

🚀 Future Improvements:

Implement error handling 🛠️: Enhance error handling to provide a better user experience in case of API request failures. Add more interactivity and sharing options 💬: Extend the app's functionality by allowing users to interact with advice and share it on social media. Enhance the user interface and design 🎨: Improve the visual design and user interface to make the app even more engaging and user-friendly. I enjoyed building this project and learned valuable skills along the way.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bisola Onaolapo•160
    @bisoladev
    Posted almost 2 years ago

    Great implementation !! I love the fact that you created your own spinner from scratch The only observations I would give are:

    1. I think one divider image would be better and then adding a max width to it so that it doesn't overflow in mobile view...because your implementation though had two different images for mobile and desktop, overflows when it gets to a small-sized mobile
    2. Adding an error state, like an 'oops an error occurred message' when there is an error would be great

    Overall I think it was an awesome 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

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