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

Chat app CSS illustration

Jayas Piya•278
@jayaspiya
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Open for suggestions

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • August•100
    @Augs0
    Posted almost 5 years ago

    Really great job overall!! You managed to hit the design spec almost perfectly :) It's cool to see how everybody tackles the challenge.

    If I were to offer any suggestions, it would be to maybe add another media query. Right now, everything up to 900px has the same rule-set, as such, if you drag the screen to a mobile-ish size, you'll notice your text gets hard to read as it sits on the bottom curved shape and they are more or less the same colour.

  • Ovidiu-Antonio•3,125
    @ovidiuantonio
    Posted almost 5 years ago

    Hello,

    Very nice solution so far! The site is responsive and the phone illustration looks very nice! There are a few things that you can improve:

    • add cursor: pointer; to all the elements that are clickable (back arrow, text field, send message button etc)
    • for the text field use an input element instead of a div, for the send button use a button element, for the option buttons use radio buttons. In short, make the app "usable" so the user can select one of the options, click the buttons, enter a text

    Happy coding! Keep going!

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