locked
What's the difference between app part, web part, and client web part? RRS feed

  • Question

  • I'm developing an sharepoint-hosted app in visual studio, and deploy it. When I edit a page, I don't see the app in the app part or web part. What's the difference between app part and web part? 

    Why does the app need a client web part to show in web parts or app parts? What is client web part?

    Wednesday, August 28, 2013 8:10 AM

Answers

  • Just as SharePoint users have become accustomed to talking about web parts, Microsoft has changed the game from web parts to apps. A common question involves the difference between apps and web parts.

    From an end user perspective, web parts and apps are similar – they both provide a way to add functionality to a SharePoint-based web site.  Once created, they can be leveraged on multiple sites with proper deployment and configuration.

    The primary difference between apps and web parts is how they are developed and deployed.  Web parts are built to run within SharePoint and are deployed directly to SharePoint Servers.  Apps run outside of the SharePoint environment and are simply added to SharePoint sites. One benefit of this is that poorly built apps will not impact your site like poorly built web parts can.


    Whenever you see a reply and if you think is helpful, click "Alternate TextVote As Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Alternate TextMark As Answer

    Wednesday, August 28, 2013 1:44 PM

All replies

  • Just as SharePoint users have become accustomed to talking about web parts, Microsoft has changed the game from web parts to apps. A common question involves the difference between apps and web parts.

    From an end user perspective, web parts and apps are similar – they both provide a way to add functionality to a SharePoint-based web site.  Once created, they can be leveraged on multiple sites with proper deployment and configuration.

    The primary difference between apps and web parts is how they are developed and deployed.  Web parts are built to run within SharePoint and are deployed directly to SharePoint Servers.  Apps run outside of the SharePoint environment and are simply added to SharePoint sites. One benefit of this is that poorly built apps will not impact your site like poorly built web parts can.


    Whenever you see a reply and if you think is helpful, click "Alternate TextVote As Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Alternate TextMark As Answer

    Wednesday, August 28, 2013 1:44 PM
  • Thanks buddy... vry simple to understand....

    Friday, October 4, 2013 5:50 AM
  • The answer is copy&paste from blog at http://blog.tahoepartners.com/index.php/sharepoint-2013-apps-six-reasons-you-should-care/
    Friday, March 14, 2014 10:07 AM
  • At least, you could have mentioned your source... http://blog.tahoepartners.com/index.php/sharepoint-2013-apps-six-reasons-you-should-care/ 
    Saturday, April 26, 2014 4:07 PM
  • Why are you not giving credit to the source when you just copy and paste the text?

    /Joakim

    Monday, August 25, 2014 11:00 AM
  • Well, he's a Microsoft employee; why would he give credit to people who actually invented and developed an idea?

    PS Thanks for the link to the original document. Sidwell's discussion is excellent.
    • Edited by Xmeromotu Wednesday, October 11, 2017 4:20 PM
    Wednesday, October 11, 2017 4:19 PM