Hi
We are setting up an all fresh SharePoint environment, no SP migrations, no SP legacy and I was reading up on the SP2013 new ‘app’ model. My first thought was(is), OK we do all our customization via Apps, no need to use the ‘old’ way of workingÂ
Of course I’m not well placed (yet) to decide on the ‘no need’, hence this question to  people who actually do know what they’re talking about :Â
– Why would we want to invest/develop in webparts (full and/or sandboxed) ?
thanks again
Danny
Hi Danny,
The apps live their life kinda alone 🙂
-and with limitations regarding what they can actually do/interact with content elsewhere in SharePoint. As I see it they are very good at the presentation layer and as a visual improvement of the content. It is an application running another place than the other SharePoint content – therefore there are some security tricks you need to learn. The apps take a long time to develop as most is JavaScript/HTML5/CSS work
The sandbox solutions/webparts have most functionality and really flexible and fast to develop as you use .net language. It is limited to Work in the Site Collection you activate it in and cannot use the backend infrastructure or reach other site Collections (unless you are using search). Really good for developing stuff on-premises and Office 365.
The full solutions/webparts is only used on-premises, but have the advantage that it can interact with all SharePoint functions/features/Site Collections. The full solutions/webparts cannot be used in Office 365 and I think the idea is to depricate these in the future versions of SharePoint.
Â
Hi Danny
I will get Jesper to comment, I know he has recent personal experience of the App Model (along with all its wonders ;)).
