| title | slug | sidebar_label |
|---|---|---|
Front end system design interview - applications |
front-end-system-design/applications |
Applications |
:::info We are now part of GreatFrontEnd!
Front End Interview Handbook is now part of GreatFrontEnd! We are working to migrate the content over and you may find the latest version of this page on GreatFrontEnd.
:::
- News feed (e.g. Facebook) — Read example solution on GreatFrontEnd
- E-commerce marketplace (e.g. Amazon) — Read example solution on GreatFrontEnd (Paid)
- Chat application (e.g. Messenger) — Read example solution on GreatFrontEnd (Paid)
- Photo sharing application (e.g. Instagram) — Read example solution on GreatFrontEnd (Paid)
- Video watching website
- Mail application
- Requirements exploration
- Architecture
- Data model
- Interface definition (API)
- Optimizations and deep dive
- User experience (UX)
- Performance
- Accessibility (a11y)
- Internationalization (i18n)
- Multi-device support
- Security
Every system design interview should start with clarifying requirements about the question, which is usually left vague intentionally. Some considerations:
- What devices should the system support? Desktop web, mobile web, etc
- What's the primary device that users will access the system on?
- Which browsers should we support?
- Do we need to support internationalization?
- Does the app need to work offline?
Architecture for front end interviews are typically focused on the client-side architecture, and not on large scale distributed systems where databases, load balancers and servers are involved.
For applications, common architectures include Model-View-Controller, Model-View-ViewModel, Flux, N-tier (where data tier is on the client) etc.
:::info Read front end system design case studies
GreatFrontEnd shows you how to approach front end system design interviews with their front end system design guide and case studies. Start reading today!
:::
Client app state, which is a combination of server state (database) and true client state (non-persisted to the server).
API design for applications will refer to the HTTP/network API parameters and the shape of the responses.
With the architectural basics of the application covered, we can dive into specific areas which the application might need special attention to. Note that there almost definitely won't be enough time to cover every area, and not every area will be very relevant to the component at hand.
Showing knowledge about these areas and being able to dive deep into them are traits of senior developers.
- User experience (UX)
- Performance
- Accessibility (a11y)
- Internationalization (i18n)
- Multi-device support
- Security
Many companies blog about their technical challenges in the front end domain and these are great content to learn more about designing front end systems.
- Building the Google Photos Web UI
- Twitter Lite and High Performance React Progressive Web Apps at Scale
- A Netflix Web Performance Case Study
- A Tinder Progressive Web App Performance Case Study
- A Pinterest Progressive Web App Performance Case Study
- A React And Preact Progressive Web App Performance Case Study: Treebo
- Rebuilding our tech stack for the new Facebook.com
:::info Read front end system design case studies
GreatFrontEnd shows you how to approach front end system design interviews with their front end system design guide and case studies. Start reading today!
:::