Hi Dave, I have to break it to you, there is no sliver bullet. An app doesn't need to be a SPA to qualify as an app. In some situations, it makes sense to break up certain parts of an application into a separate 'sub-app' (a new entry-point, that can work on its own.) However that sounds like a lot of overkill for what you are asking.
In most scenarios you build your app out of modules, and 'navigate' between those parts using a router. They use an app-shell (the basic-lay-out of the page, often including navigation-menu's and the top-level router) and then pull in the part that's needed. The app-shell will take care of the login, and stuff like that. For myself, I usually keep registration a separate page/app. Also, most larger projects also come with a separate 'management' page/app. It makes no sense managing system-settings and the users themselves, from the 'inside' of a app. Hope this helps you a bit. If you have questions, don't hesitate to ask them! Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
