Designing Around Client Logic & Patterns of Web Applications
Designing around client logic
Therefore, a problem for many client-side app frameworks is sharing common state information among otherwise unrelated small components across the page or the app.
Both of these options have their benefits and drawbacks. There’s also a middle ground where individual web pages might have their rich interactions, but we let the server handle the transition between pages.
Patterns of web applications
To make this architecture discussion more concrete, let’s look at how these decisions might play out in a specific web app. Slack is a real-time collaboration and chat application that runs in a browser. Later in the course, we’ll look at how an application might handle real-time chat notifications. For now, let’s focus on two user interactions:
When users click in the sidebar to remain in chat but change the Slack channel they are looking at.
When users click to view their profiles, it completely removes the chat interface and replaces it with something more like a form.