Premium

@Input/@Output vs shared service for Angular component communication

Guided tradeoff battle · Updated Mar 29, 2026

Challenge summary

An Angular page has a parent container and a few child UI components that need to send user actions upward and receive current state downward. Would you use @Input/@Output or a shared service?

What you'll practice

  • Compare the available options against the prompt constraints.
  • Defend one direction while acknowledging its main downside.
  • Explain when an alternative becomes the stronger choice.

What Premium unlocks

Premium unlocks the option matrix, scenario-specific evaluation, answer walkthrough, and follow-up trade-off discussion.

Free related practice

Upgrade to FrontendAtlas Premium to access this tradeoff battle. Already upgraded? Sign in to continue.