3. text
MVC
Most Monolithic applications use MVC Model
â˘
â˘
â˘
â˘
Provides a well proven structure for web applications
Model - logic & data
View - Presentation layer
Controller - Glue & Routing
6. text
Forces Influencing the View
⢠Marketing - Trend to ânativeâ like apps UX
⢠Performance - Offload some of the work to
the client
⢠Business - Web applications need more
hits to make a $
7. text
The View Evolution
Move to Single Page Applications
What makes it possible?
⢠Improved browser JS performance
⢠Improved client hardware
⢠HTML 5 Standards
8. text
Single Page App
Move all presentation logic to the client
Result:
â˘
â˘
â˘
â˘
â˘
We get a âStandaloneâ Client
The âVâ in server MVC almost disappears
Client becomes more complex
Asset management importance hits a new peak
Both server and client become more robust
11. text
New Web Client Complexities
⢠Lots of assets (JS, CSS, HTML, Images)
⢠Lots of 3rd party libraries
⢠Lots of events and logic
⢠Complex data models and logic
⢠State management
⢠Routing management
13. text
Web Apps Development Keys
⢠Start treating web apps with respect (as software)
⢠Adopt standard development flows and tools
⢠Test your code
⢠Separation of concerns and concise modules
⢠Manage assets with designated tools
⢠Use dependency management tools
18. text
Summary
⢠Web apps should be treated as software
⢠Web Client should be developed as a separate
project
⢠Coding paradigms (MVC) should be applied to web
apps
⢠Use tools to increase efficiency