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

Angular Chat app with Sass using Grid & Flex

Karim A C•150
@ackuser
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi all, first of all thanks for the platform and support.

Well, I have used Angular to create components in some visual entities for reuse them as much as possible.

Grid was used for positioning the two main design with Media Queries as well. Then, I made responsive components flexing them with Flex.

Mainly, I did the phone & comments playing with shapes in Css and positioning them through margins, positions, relative units, etc.

One thing I really struggled was the creation of effects delayed with interpolations in Sass. In fact, I haven't learnt yet if it is possible to know how many elements are belonging to a class (See src/app/phone/phone.component.scss L43 ). My idea was to get this parametized @for $i from 0 through 7 { ==>
@for $i from 0 through NUMBER_OF_ELEM_WITH_CLASS {

Can anyone know how to do that?

Anyway, I have tested on Chrome & Firefox. Finally, I checked with a real IPhone 7 where I found problems related with scroll, although I was able to solve.

Any feedback would be really appreciate it, many thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey, Karim A C! 👋

    Good job on this challenge! 👍

    Your CSS illustration looks good and your solution is responsive! 🙌

    I suggest,

    • Decreasing the space between the CSS illustration and the text of the page and setting the text-align property of the text to start in the desktop layout of the site (to match the original design more closely).
    • Not immediately switching to a mobile-friendly layout right at 1440px since your solution still has plenty of space to accommodate the desktop layout for a few hundred pixels after that.
    • Making sure the text of the page doesn't get hidden behind the CSS illustration on screens with small viewport heights.
    • I'm not familiar with Angular JS, but I used CSS to create the messaging animation for this challenge. It's easy to create a simple animation for all of the messages and then set different animation-delay times for each message. You can do the same thing in Sass, of course, without any trouble.

    Keep coding (and happy coding, too)! 😁

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub