Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Link-sharing app built in Angular 17 and Firebase

angular, firebase, typescript
Curtis•930
@webguy83
A solution to the Link-sharing app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


In developing this application, I embraced the cutting-edge features introduced in Angular versions 16 and 17, which significantly enriched my development experience and the app's functionality. I ventured into the realm of reactive programming with Angular Signals, a new feature that simplified state management and asynchronous data handling, allowing for more intuitive and declarative code patterns. The introduction of built-in control flow syntax, such as @if and @else, replaced the traditional *ngIf directive, streamlining template logic and enhancing readability. These constructs enabled me to conditionally render components with greater ease and clarity. I also adopted new injectable techniques that Angular 17 brought to the table, leveraging the inject function for more flexible and decoupled service consumption within components and services alike. Furthermore, my journey included mastering advanced Angular and RxJS concepts for robust state management, securing routes with guards and resolvers for data pre-fetching, and integrating Angular Material for a polished UI. Continuous deployment via GitHub Actions to Firebase Hosting was another milestone, underscoring the importance of CI/CD pipelines in modern web development practices. The project also deepened my understanding of Firebase Authentication and Firestore, incorporating stringent security rules to protect data integrity. Through implementing these advanced and new Angular features, alongside Firebase's scalable infrastructure, I've crafted an application that not only meets modern web standards but also leverages the latest developments in the Angular ecosystem, marking a significant milestone in my web development journey.

I built this using Firebase's authentication along with Angular state services, directives for UI buttons and some visuals, resolvers for API preloading, auth guards, Firebase storage to store images, and a lot of more advanced features.

This was the most difficult brutally tough application I have built so far but definitely rewarding! Feel free to post your social media links on here and share with me. I followed all the requirements and added a Sign Out button as well. Here is mine right here:

https://frontendmentor-linksharing.web.app/preview/h1SCKoae6tQdqdeX7vFZEd5ly6i1

I am saving all of this in Firebase with strict Firebase rules so everything is very secure. If you'd don't feel like creating an account you can login as guest@guest.com and password is 12345678. Would love to see all of your links though on your own accounts! :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Curtis's solution.

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.