SharePoint Add-ins Vs. Web Parts (Comparison of App Model)

If you are SharePoint visual web part developer and starting up ground works with the SharePoint apps development, following comparison would be useful when mapping your previous knowledge with this.



SharePoint Add-in SharePoint Web Parts
Installed on Runs independently without sitting on the SharePoint (Client) SharePoint front end servers (Public facing servers)
Weight of the code Client side scripting and weight of code does not impact the SharePoint Depends on the code based provided with the web part
Coupling with the SharePoint server Loosely coupled with SharePoint and runs independently Tightly coupled with SharePoint Server and cannot survive without it
Client side scripting Highly involved Less impacted on most developments
Server side scripting Possible Not Possible
Mounted to SharePoint Using iFrame Using ASPX controls
Pre configuration App catalog and some other configurations required No
Distribution via common place (App ) Capable No
Integrating with other programming languages Capable with other programming languages such as HTML, JS Frameworks, PHP, Java and etc. Mostly .Net related technologies


Further references


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s