I don't understand why Microsoft calls Document Libraries and Custom Lists apps in SharePoint 2013 Preview - doesn't it contradicts the concept of isolation of an app from the parent site? It's my understanding that one can not achieve the same level of integration into the parent SharePoint site within an app. Is it just confusing terminology that Microsoft used for custom lists and document libraries or am I missing something about app capabilities in SharePoint 2013?
|
Microsoft tries to make SharePoint understandable for all users. So SharePoint is simplified into three concepts:
The apps you create don't get the same integration into the "Host Web" as list/document libraries, but that's in fact to keep things similar:
To many end users Lists and Libraries are custom functionality similar to apps. Your "real" app can show itself in the "Host Web" in three ways.
And if your app gets the permissions it can in fact create lists, libraries and anything you want on the "Host Web", but if you want to sell your app as 3rd party you should probably try to limit your permission requests. |
|||||
|
|
The content of a HostWeb in the form of Document Libraries and lists should remain just that. But a list template or doc library template or custom view for a list/library could be an app. Then it would be transferable to different webs. It definitely seems confusing! |
|||
|
|
|
As far as I understand it, in Office 2013 and SharePoint 2013 Preview, everything is an app. OOTB lists and libraries are now referred to as apps as well, so the fact that a custom list is called that is not surprising. Now, this is still different from an app on the app store, but the terminology of the product still refers to lists and libraries as apps. |
|||
|
|
