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

Invoice App Angular, Tailwind CSS, RxJS

angular, tailwind-css
Parth Manhas•340
@parthmanhas
A solution to the Invoice app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


With this project I used only RxJS BehaviourSubject for handling states, could anyone please guide if this can work for large projects? (I am not able to figure out the use case for ngrx or will I eventually switch to ngrx?)

Thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Curtis•930
    @webguy83
    Posted almost 2 years ago

    Hi Parth, good effort on this beast of a project. Don't worry about the need for NGRX as it's only needed when RXJS solutions aren't good enough. This happens when applications get to enterprise level. Usually then it's best to look into NGRX so need to pursue it on these challenges.

    I just finished doing this project too and I wanted to share some things I noticed when seeing your app:

    • on my mobile device the layout breaks pretty bad especially when displaying the card. Text is crashing into each other

    -it also breaks on the detail invoice view. If you see the Figma they do something quite different on mobile. Perhaps look at a responsive solution for that. In Angular I would advice you use the Breakpoint service to dynamically inject classes on breakpoints. You can look it up in the docs.

    • I didn't even see a Mark as Pending button on mobile view as it was cut off completely. This was only visible on desktop. A mark as pending button isn't needed anyway. Anytime a user saves and submits a form it goes to pending always.

    • they mention ids on the cards should be 2 numbers followed by 4 letters. Using the index array value isn't a good solution for ids and can be a real source of bugs

    • when the slidenav section is out it creates two scroll bars one on it and one behind. I even saw the header scroll down and the content behind the slideout nav was showing from behind it. Very visible from mobile view.

    • in your form instead of Payment Due you can just use Payment terms selection box and it to the invoice date to calc the payment due. On a sidenode for your Angular Material calender you can inject your colour themes into it. I recommend using Angular Material theming for the colours. It is amazing.

    • your form needs validation messages for invalid email, forms not having content, etc

    • I also noticed tons of vw being used on widths as well. This could be the source of your issues on mobile device. It's always best to avoid using vw for pretty much everything and never use hard coded widths at all like px, rem, em, etc.

    You can look up Kevin Powell on YouTube as he has some amazing tutorials on fixing responsive issues. All the best!

    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 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