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
Alright – I understand that as far as functionality goes (on-premise) apps don’t fall much behind web parts.
In reply to Steven. We will go for out of the box if possible – once that’s not an option we would preferably want 1 solution model. It’s not only the time to invest in learning the different models, also the skills needed to maintain are important.
We are thinking better to invest in 1 model and get that fully understood than a little bit of everything.
The loose coupling and shielding of apps is also appealing, the ease of deployment etc.. without impact on the actual SharePoint env etc…..
I’m coming from a ‘low coupling, high cohesion’ component oriented world, you understand why I find apps so appealing (at first sight)
