Frontend Infra Book
  • Why I Wrote This Guide
  • Mock Interviews
  • Development Roadmap
  • Product/Nonfunctional Requirements
  • Technical/Functional Requirements
    • Performance
    • User Experience Tracking
    • Backend Integration
    • Security
    • DevOps
    • Other / Unsorted
  • Design System & Common Components
  • Examples
    • Trading System
  • Topic In Depths
    • Containerization
    • Data Stack
    • Tools and Packages List
  • Common Solutions
  • Success/Failure Stories
    • Comp At Startups
    • Scaling FE Teams - My HOVER Story
  • Other Resources
  • Environment Setup
  • About The Author(s) + Contributing
  • Interviewing for FE
    • Getting The Interview
    • Negotiation Tips
    • How RSU's Work
    • Moving Up in Your Career
    • FAQ
    • Companies
  • Culture
  • What Matters in Company Culture
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub

Technical/Functional Requirements

This is really the main job of the FE Architect, gathering as much information on technical requirements aszx possible, before the team starts building. This is an enormous topic which is very specific to the type of app you are building. I will go through some common conciderations, as well as a few types of common apps.

The requirements for a FE App are very different than a BE service. Yet you will closely interacting with the BE team on many considerations.

Todo

  • Server Side rendering for public pages? Google optimization

  • What metrics are we optimizing for

    • Track metrics

Progress Web App? Offline mode No internet connection

Improving Build Speed

  • Yarn Cache

  • Docker image cache

  • Webpack Optimization

  • Sourcemaps?

PreviousProduct/Nonfunctional RequirementsNextPerformance

Last updated 3 years ago

Was this helpful?