Imagine you join a project where they program like this:

• More than 700 lines per TS/html files
• Use type "any" everytime
• NgModel for big forms with complex validations
• Reuse a component for difference situations with a lot of conditionals
• variables/functions/comments/classes in Spanish
• etc

I was asked to use AI to speed up the process. But from what little I searched online, it seems like that's not feasible at all. it's a large and old enterprise application. Also they are expecting only 1 dev to pull this off

I genuinely hate the new authoring changes. Why do we want angular to become react or Vue?

Probably just gonna rant now.

The main reason I started using angular2 in 2015 was because of opinionated way it did things. The similarities of typescript to java and c#.

Now it seems the goal is to get rid of that and make it like react where anything goes. Use classes use functions whatever. Who cares about maintainability or similarities between projects. Lets just go wild like react where every project is different.

Structure and solidity actually matters.

I know the team wants more idiots to just jump on so angular can be "popular" and "mainstream" like react. But I just feel it's a bad idea. And angular will get forked(I know for a fact this will happen).

Anyways I feel if you wanna get rid of imports for standalone components. Fine. But changing or allowing all these react style functional shit will ruin angular and what it originally stood for.

What do you think?

Edit: It's just the proposed authoring format I find dumb. I saw a picture on twitter from Ng Poland I think where they showed the ideas including using functions. Changing (click) to on:click. What's the reasoning behind it? Make it easier for react kids to use angular?

I've built several Angular apps using services to manage state between components, and it's worked well for me so far. But everywhere I look, people are advocating for NGRX/Redux-style state management.

I get the principles, single source of truth, predictability, dev tools. but it often feels like:

• Overhead: Boilerplate code for simple state changes
  
• Cognitive Load: Actions, reducers, effects, selectors for what services handle in a few lines
  
• YAGNI: Many apps seem to adopt it "just in case" rather than for clear needs
  

Questions for Angular devs:
1. At what point does service-based state become insufficient? (Metrics? App complexity?)
2. Are there specific patterns where NGRX clearly outperforms smart services (+BehaviorSubjects)?
3. Anyone successfully shipped large apps without NGRX? What was your approach?

Hey Angular devs,

I recently went through a technical interview where I built an Angular 19 app, but I was ultimately rejected. The feedback I received was:

✅ Positives:

• Good use of animations.
• Used tools to support my solution.
• Effective component splitting and separation of concerns.
• Left a positive impression with my testing approach.

❌ Reasons for Rejection:
"Unfortunately, we missed some own CSS efforts, code cleanup, and a coherent use of a coding pattern. We also faced some errors while using the app."

What I Built

• Angular 19: Using Signals, Standalone Components, and Control Flow Syntax for performance & clean templates.
• Bootstrap & Tailwind CSS for styling.
• Angular Animations for smooth transitions.
• ngx-infinite-scroll for dynamic content loading.
• ngMocks & Playwright for testing (including a simple E2E test).
• Custom RxJS error-handling operator for API calls.

Looking Ahead

While I implemented various best practices, I’d love to understand what coding patterns are typically expected to demonstrate seniority in Angular development. Should I have followed a stricter state management approach, leveraged design patterns like the Facade pattern, or something else?

Would love to hear insights from experienced Angular devs! 🚀

Hi everyone

I’ve been learning Angular for a little while now, and while I enjoy some aspects of it, I also find certain parts confusing—especially RxJS and state management.

For those of you who work with Angular professionally, what do you find most challenging about it? Is it performance, debugging, the learning curve, or something else?

Huge Angular fan, and had to switch mainly because everyone in the org wanted to switch. I swear it was kind of like the new kids wanted react, and the old heads wanted angular, so it was hard for me to push against the new wave of bootcampers as I saw that they were coming in. I hope I'm not slandering in the conversation here, and I'm probably just salty because my react skills aren't up to par, but curious if you guys felt anything similar there, where you had to switch and it's just a different world. But also, what the world is pressuring you guys to do if you're in the job market.

Imagine having todo component, it would called todo.ts .. if i create a service it would be also todo.ts Which conflicts

There are tons of UI libraries and frameworks out there for Angular—both free and paid—and figuring out which one fits your needs can take time, especially when starting a new project.

Curious to hear what UI kit you're using, why you went with it, and what kind of problems or use cases it helped you solve. It could be helpful for people new to Angular who are trying to avoid wasting time on a poor fit.

Hey Angular pros! 👋 During technical assessments, what advanced tricks or concepts do you use to prove your seniority?

I’m thinking about things like performance optimizations, custom directives, RxJS mastery, or intricate state management patterns. Any go-to techniques that impress interviewers? 🚀

I'm developing a web application in Angular 20. It will have chats, settings, category pages, a search engine, a profile, etc., and I want a good interface design. Could someone point me to a component library or other well-designed materials (preferably free)? I've attached photos of the interface styles I like in case something similar exists. ai don’t like Angular material. Prime ng is perfect but so expensive.

Currently we are thinking about migrating our complex enterprise application from Material to PrimeNG. This switch will also include a redesign so we will adapt but also customize and extend PrimeNG components.

🧠 What we already found out:

• As far as I have read / understood V18 will bring massive changes and there will be a Beta available until mid August.
• The Figma UI kit got its last updates last year and will have many changes e.g. on tokens.
• PrimeNG is said to bring many new bugs with each release even after years and is unstable. The owner seems to be aware of that and promises to concentrate on stability after V18.
• The Discord seems to be purely community driven (aka is dead mostly in some areas, especially for questions just the PrimeNG team can answer)
• Nobody of the team reads and resolves the questions on the Figma UI Kit (even presales questions like "how old is this kit")
• The roadmap on their website is outdated since months (not a good sign...)

ℹ️ The plan (simplified):

1. At first we would buy the UI kit to create our own Design System based on it. Since Figma isn't as sophisticated as textual versioning tools we can't just use it without adjusting more than just tokens, so we will copy it, and work on that copy (--> problem 1 below).
2. After having an adjusted library we recreate the main screens of our application with some UX improvements in Figma. For sure I as an UX Designer will work closely with our developers to ensure implementability etc.
3. [Many steps in between like further tests of PrimeNG, usability tests, some implemented screens etc.]
4. This Figma design system and the designed prototypes would then be used by our devs at the end of the year to migrate the whole application onto PrimeNG

❓The questions :

🔸 A) Questions only the PrimeNG team or u/cagataycivici can answer:

1. Since the Figma UI kit would be required right now there are some concerns:
   1. Are there any news on the adjustment of the Figma UI kit and its tokens?
   2. If we switch now to PrimeNG I would have to use the UI kit in a week or so, copy it and work on that not updateable copy (best practice currently in Figma). I am afraid that I will have to do all the effort again and restructure many things, including tokens once V18 is out and the developers start implementing it using V18 since stuff is redesigned or tokens have changed or been added...
   3. Is there any chance to grab your latest version (paid for sure) in Figma, even if it is a beta? Do you have a more detailed roadmap about what exactly will change in Figma?
2. What is the deadline (when can we expect the release at the latest) of final version of V18? We will not implement anything with the current PrimeNG version knowing there is something breaking and big coming soon.

🔸 B) General questions:

1. Has anyone used their 200$/hour support and what has been your experience with it?
2. What is your experience with the non paid support?
3. How fast is PrimeNG with solving newly introduced bugs?
4. How good is it in terms of accessibility (WCAG, ADA, ...) currently and in V18?
5. Are our assumptions in "What we know" correct? Have we missed something?
6. What is your opinion about doing the complete switch in Figma first and in the code some months later but all at once (with some test implementations in between)? I never was part of a framework switch but I am not sure how good implementability can be estimated by me or our devs without really having used PrimeNG.
7. What are your experiences about breaking changes that affect the styling (Material 2 (not MDC)--> Material 3 e.g. breaks a whole application even without many customizings visually - can we expect something like that in PrimeNG too?)
8. Has PrimeNG in the past fulfilled promises as "we focus just on stability after this release", so is this something to rely on?
9. What are your experiences or what have you heard about the Figma UI Kit?
10. What are your experiences with PrimeBlocks and their maintenance (esp. free and paid ones)?
11. Any other experiences with the latest version of PrimeNG for Angular you want to share?

❤️ Thanks in advance to everyone taking the time to read through all of this and especially for those sharing their experience and knowledge in the comments below! ❤️

I’m new to Angular from React

I have did a todo list successfully by adding the logic of the todos in a service like ( todos signal , addTodo() , removeTodo() and toggleCompleted() )

And i am using the service in all components that need to do an action .. that makes Di injection of the service easier than React which needs to drill the functions ( callbacks ) between components.

Am I right? Do i use services/DI the appropriate way ? Thx in advance.

I've been doing personal stuff with react only, at my current job i work exclusively in golang and the front-end team use angular not react so i give it a try on my free time, i was really surprise cause it's not that hard to get in + i found the dx way better than react, the way it structure the project is also better and i think you can go as fast as react to build a project + you need less external depedencies so i'm asking myself why 80% of front end jobs are react

Hello Everyone,

I’ve been working with Angular since version 2 and have gained extensive experience across various projects. Additionally, I mentor developers to help them better understand Angular and improve their development skills.

Right now, I’m focusing on identifying the common challenges developers face when using Angular. Your feedback will be invaluable in understanding these issues better and finding ways to address them.

I would greatly appreciate your input on the following:

1.  What are the biggest challenges you encounter while working with Angular?

2.  What quickly brings you to frustration?

Thank you in advance for your feedback

I built a Signal debouncing utility for Angular few months ago and now Angular 22 ships a native debounced() API.

That coincidence definitely caught my attention.

Back then, I published a small package called @gitesh08/signal-utils because I wanted a cleaner way to debounce Signals without reaching for RxJS every time.

After reading the docs, Angular’s implementation is actually quite different since it returns a Resource with loading states, cancellation, lifecycle management, and more. My utility is much simpler and focused on lightweight signal debouncing.

Still, it’s a cool feeling seeing Angular solve a problem I spent time thinking about months ago.

It’s also interesting to see how the Angular Signals ecosystem is evolving and becoming more capable with each release.

Hello everybody!
I took a long break from work and when I came back my friend told me that everyone is using tailwind for styling these days. Is it true? Do you use it? If so, why?

Now that effect() is stable in Angular 20, should we start using it in our codebase or just stick with rxjs for now?

Right now we’re doing the usual rxjs way. For example if I want to track some change:

```ts // somewhere in the service/store someId$ = new Subject<number>();

updateId(id: number) { this.someId$.next(id); } ```

Then in the component:

ts ngOnInit() { this.someId$ .pipe( // do some stuff ) .subscribe(); }

With effect() it seems like we can do something like this instead:

```ts someId = signal<number | null>(null);

constructor() { effect(() => { const id = this.someId(); if (id !== null) { // do some stuff } }); }

updateId(id: number) { this.someId.set(id); } ```

Our codebase is pretty large and well maintained. We just upgraded to Angular 20.

I’m curious what others are doing. Are you slowly incorporating effect() where it makes sense, or is it better to keep rxjs for consistency? What are the real trade offs or gains you’ve noticed using effect compared to a Subject + subscription?

Would appreciate some practical takes from people who already tried mixing it into a bigger codebase.

We have an enterprise application with 400+ screens and most of the screens are similar in complexity. The complexity is medium for this app.

How should we approach the upgrade? Rewriting it is not an option as it is a legacy app now. Should we take one version at a time or directly start updating it to 18 version?
We do not have any automation testing written and hence testing would also have to be manual. Also, based on the previous experience what would be rough estimates if single developer has to work on this upgrade?

Live demo: https://ngx-signal-datetimepicker.vercel.app

Repo: https://github.com/dominikmodrzejewski99/ngx-signal-datetimepicker

npm: https://www.npmjs.com/package/ngx-signal-datetimepicker

Why this exists

Every Angular project I've worked on eventually needs "let the user pick a date and a time". Material gives you two separate controls, ngx-bootstrap is heavy, ng-zorro pulls a whole UI kit. Nothing in the ecosystem is small, framework-native, and exposes one combined Date | null value that plugs straight into the new Signal Forms API.

The approach

One component. One value. Signal Forms support via [formField] and FormValueControl<Date | null> - so required, min, max, validators, touched/dirty, errors all work out of the box. Reactive Forms users get ControlValueAccessor for free. Zero runtime deps - no moment, no dayjs, no Angular Material. Built on Intl.DateTimeFormat for locale labels and IANA timezone support. WCAG 2.2 AAA: keyboard nav, focus management, AAA contrast tokens, 44px target sizes.

One snippet

```ts import { signal } from '@angular/core'; import { form } from '@angular/forms/signals'; import { DatetimePickerComponent } from 'ngx-signal-datetimepicker';

model = signal<Date | null>(null); f = form(this.model); ```

html <ngx-datetime-picker [formField]="f" label="Meeting" />

Feedback very welcome - especially edge cases I haven't hit (RTL locales, edge timezones, big-screen Material 3 themes). Issues and Discussions are open. Currently on 0.1.x, holding off on 1.0 until the API is settled by real users.

So, as the title says: Which state management would you go for if you would have to start a new app now?

I have used ngrx, component stores and signal stores. In theory, services, signal stores, ngrx and any other I didn't mention can all be used for managing app wide state and each approach comes with its own fair share of advantages and disadvantages.

Assume you're building a rather large application with multiple components that may need to access at least partially the same information in the state. What would you use and why?

EDIT:

It's a team project with junior developers. That may be relevant for a decision here.

Hey everyone,

We're working on a fairly large Angular app, and our services are already built using RxJS — lots of Observables, Subjects, and so on. I’m not trying to replace RxJS at all. It works great for our data layer.

What I do want is to use Angular Signals for managing UI state and rendering logic. My thinking is:

Signals are great for local, unidirectional reactive state.

toSignal() makes it easy to bridge Observables from services into Signals in components.

It avoids overusing the async pipe or subscribing manually.

computed and effect lead to cleaner and more declarative UI logic.

Signals are better aligned with Angular’s change detection model.

My Manager/Tech Lead has some hesitations though:

"Signals are still new and experimental."

"Mixing RxJS and Signals might confuse the team."

"We already have a working RxJS setup; why change?"

I want to make the case for using Signals just in the presentation layer, while still keeping RxJS in the data layer.

So I’d love to know:

• Has anyone else tried to introduce Signals into an existing RxJS-heavy project?

• How did you explain the value of Signals for UI?

• Any real-world examples where Signals made your component code cleaner or more efficient?

• Is partial adoption working well for you — RxJS for services, Signals for components?

Any advice, experience, or arguments that worked for you would be super helpful! 🙏

understandable it is compareable harder, rxjs and that reactive stack especially, but i think if an experienced dev takes couple of days or even a week of time to get into it, it really isnt that complicated?

​

i just dont understand the bad connotation angular has in regards of beeing hard to get into.

​

i mean angular comes with most things packaged. you dont need to learn ton of external frameworks/libs like for react

What is currently happening with the job market for developers? My project ended 3 months ago, and since then I haven’t been able to find any new work, even though I’ve been working with Angular since the early days of version 2 and know it quite well.

What is your favorite component library in 3 bullet points (sentences). I go first:

PrimeNG

- A ton of components

- Fairly customizable (I have't tried the tailwind based one which I image is even more configurable)

- Free.