Looking through Microsoft's tutorials, it seems like they used SPA in fairly simple scenarios. i. To filter or update a single list.
Let's say I have a slightly more complex interface where I can have several lists, several add screens and several wizards, etc. that guide the user, although some processes.
Will the preferred approach for a single-page application have multiple controllers and views for each area of the system, i.e. if I have a user management area - it can be one controller / view, then maintaining the user profile can be another controller / View.
Consequently, user experience will be navigation between pages, but on a page where they want to perform certain operations with all AJAX?
If such an application was truly SPA , I think that in the end I get tons of divs on one page, reflecting the user interface for each area on my system. Is this page potentially huge?
I think I could compare what I'm trying to achieve by comparing it to FaceBook ? I assume, however, that they load views through AJAX on the fly, so foot prints are relatively small.
source
share