Home
About Us
Advertise
Printable version
Apps for SharePoint
By Phil Jirsa
June 17, 2013 —
One of the most talked-about features of SharePoint 2013 is the introduction of Apps. Apps are basically Web applications that can be hosted in the cloud and have their functionality exposed from a SharePoint site. Implementing a custom solution as an App can provide many benefits for your environment. Some limitations do exist, though, and Apps aren’t always the right tool for the job. Understanding the App Model and its place in your SharePoint environment is important for any SharePoint developer, and a must-have tool on your belt for developing SharePoint solutions in the cloud.
What is an App?
An App for SharePoint is just a Web application. So what makes it so special? In some ways there is nothing special about it, and that’s a good thing! Developing solutions for SharePoint 2007 and 2010 requires a lot of specific knowledge around SharePoint as a platform. Apps can remove a lot of the dependencies and complexities around SharePoint itself, and boil them down to traditional Web development. This will open the door to a whole new audience of Web developers who now won’t have to worry about the intricacies of SharePoint.
Another way that Apps aren’t “special” is in what technology you can use, or where you can host them. An App for SharePoint doesn’t have to be limited to an ASP.NET Web application with Web Parts on a page; it can be any type of Web application you want! You could write an App in PHP, .NET MVC or even Node.js. You also have a choice in where to host that application.
The fine print
Although Apps do provide a good deal of flexibility and opportunity for developers, there is one limitation worth mentioning: Apps are not allowed to run any custom code on the SharePoint server. That is, you cannot deploy any compiled code to the farm with an App. All interaction between your App and SharePoint must use client-side APIs, OData or REST.
Initially, this seems like a pretty big hurdle to overcome. However, many improvements have been made to the client-side APIs to provide as much capability as possible. Also, protecting the SharePoint farm from malicious code or poorly performing code is another major benefit of this restriction.
Apps are not a total replacement for traditional SharePoint development; in fact, many customizations will still require that. I see Apps as a development pattern to effectively encapsulate and distribute custom functionality for SharePoint sites. Much like mobile apps allow users to accomplish specific tasks on their phones and tablets, a SharePoint App will now let us say, “There’s an App for that.”
Want to learn more? Find out about creating Apps for SharePoint 2013 .
Phil Jirsa is a SharePoint developer at Rackspace.
Share this link:
https://sptechweb.com/link/60791
Related Articles
Customizing SharePoint Online Using SharePoint Designer, Part 1
Once you get a handle on SharePoint Online, the question becomes: How can I modify it to suit my needs. First of two parts.
Planning your search strategy is more important than ever
Enabling everyone in your organization to find content within seconds creates big ROI potential.
Kapow Software and CapTech partner to automate SharePoint content migration
Combination enables customers to cut costs, improve data quality and expedite projects
Add comment
Name*
Email*
Country
United States
Canada
Afghanistan
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua & Barbuda
Antilles, Netherlands
Arabia, Saudi
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas, The
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
Brazil
British Virgin Islands
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Cook Islands
Costa Rica
Cote D'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
East Timor (Timor-Leste)
Ecuador
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Falkland Islands (Malvinas)
Faroe Islands
Fiji
Finland
France
French Guiana
French Polynesia
Gabon
Gambia, the
Georgia
Germany
Ghana
Gibraltar
Greece
Greenland
Grenada
Guadeloupe
Guam
Guatemala
Guernsey
Guinea
Guinea-Bissau
Guinea, Equatorial
Guyana
Haiti
Holland (see Netherlands)
Honduras
Hong Kong, (China)
Hungary
Iceland
India
Indonesia
Iran, Islamic Republic of
Iraq
Ireland
Israel
Italy
Jamaica
Japan
Jordan
Kazakhstan
Kenya
Kiribati
Korea (North)
Korea (South)
Kuwait
Kyrgyzstan
Laos
Latvia
Lebanon
Lesotho
Liberia
Libya
Liechtenstein
Lithuania
Luxembourg
Macao, (China)
Macedonia, TFYR
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Martinique
Mauritania
Mauritius
Mayotte
Mexico
Micronesia, Federated States of
Moldova, Republic of
Monaco
Mongolia
Montenegro
Montserrat
Morocco
Mozambique
Myanmar
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
New Caledonia
New Zealand
Nicaragua
Niger
Nigeria
Niue
Norfolk Island
Northern Mariana Islands
Norway
Oman
Pakistan
Palau
Palestinian Territory
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Poland
Portugal
Puerto Rico
Qatar
Reunion
Romania
Russia (Russian Federation)
Rwanda
Saint Helena
Saint Kitts and Nevis
Saint Lucia
Saint Pierre and Miquelon
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia & Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
Spain
Sri Lanka
Sudan
Suriname
Swaziland
Sweden
Switzerland
Syrian Arab Republic
Taiwan
Tajikistan
Tanzania, United Republic of
Thailand
Timor-Leste (East Timor)
Togo
Tokelau
Tonga
Trinidad & Tobago
Tunisia
Turkey
Turkmenistan
Turks and Caicos Islands
Tuvalu
Uganda
Ukraine
United Arab Emirates
United Kingdom
Uruguay
Uzbekistan
Vanuatu
Vatican City State (Holy See)
Venezuela
VietNam
Virgin Islands, British
Virgin Islands, U.S.
Wallis and Futuna
Western Sahara
Yemen
Zambia
Zanzibar
Zimbabwe
[Not specified]
Compose