It has been some time since SharePoint 2013 came out bringing us the new App Model. There is a nice number of Apps in the Office store already and it seems to me that this model is starting to catch up among us developers.
For me it is simply great, especially in the SharePoint Online. What are your experiances and how do you like the new App model?
Well at first when I looked at app model, I hated the fact that SharePoint developers are no more C# developers but Javascript developers, Imagine Microsoft has asking all sharepoint developers who are developing farm solutions from past 10 years using c# to forget c# and learn java script 😛
But after looking at that app model is flexible and do support server side development using Provider hosted apps, It will add more developers from Java, PHP or others in our community and we should see more and more apps as app model become mature.Â
It’s really Good features I appreciate Microsoft but lots bugs are left . However, as someone who develops custom solutions for clients they can use as central solution across enterprise Quick & easy as on demand . ist quick turnaround, app model you can great for developer and admin for small to big enterprise  within budgetÂ
 Cheers
Kamal Pandey
MCSE MCM,MCPD,MCITP, MCTS, MCP,ITILv3, ECMP, SME
The App model is a necessary evolution. SP Sandboxing got just a little more love than CAS policies, and people just never understood that SharePoint is a presentation tier, not the place for logic and data access (unless you’re building a UI for a list).Â
The model is okay though riddled with compromises (IFRAMES? Really?), and configuration in the enterprise is awful. Wildcard DNS and wildcard SSL certs for giantcompany.com? Bwahahahah, yeah, like that’s gonna happen. You’re better off waiting a few weeks to months for a new public domain name to be approved by IT, marketing, legal, etc.- at least it’s right there in the official guidance (e.g. ContosoApps.com).
One App store per farm without any security or audience targeting is a painful constraint. I love the Service Application model, I just wish more services actually implemented the model completely (ULS was allowed to set some lousy precedents) and didn’t stop at the ones needed to scrape by on O365.
Most of what I like about Apps are the parts that aren’t the App model: CSOM and REST. And best of all, the fact that logic and data access are pushed right out of SharePoint.
I think it offers a way to get what would have been a simple list or workflow in a single site out into to more reusable model.
Think in terms of holiday requests etc
It has a long way to go but it’s a start, lets just hope it’s in the next version 🙂
Seems people here like the Apps model as of my comment. In my humble opinion, I don’t like such a model because it’s a bit more complicated. You may know of one of the capabilities such as client-side object model and non-impaction at the server side. Well, that’s the ultimate principle in SharePoint 2013. I’ve been working on a few SharePoint 2013 development projects and realize that even it’s a bit easier to make the app but it as well has some constraints in some cases in which the security and performance get taken into consideration. Nobody can admit that putting your app on the cloud is faster or securer than the one developed as a WSP solution typically. Another thing came up is the accessibility through app.
At the end of the day, once you get your hands dirty on SharePoint 2013 project, you will probably realize how complex the new model is. Of course, that’s not at all, just a few case. I would love to discuss and learn more about the new architecture of the model.
-T.s
