Hi Neelesh, Well, my standpoint is quite neutral to this. It has ups and downs. I think it mostly depends on your use case, and how much interaction (if at all) is needed between tabs. De downside is, that you are essentially booting up your app mulitple times. This comes with an added memory and systenresources for your customers. Also, interacting between browser tabs is a bit harder, as it is for tabs in the same page. The upside is, that your user ends up with multiple copies of the app, so they can compare between tabs. (or even put them side-by-side)
Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" 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.
