andrew connell

Andrew Connell

training

Microsoft Cloud Show

Overview

All resources required to implemented app stored in an AppWeb & served up by SharePoint

One page, multiple screens yet no traditional page refreshes

Put all JavaScript libraries / vendor scripts in /Scripts
- Just like References is for server side assemblies
Put your custom JavaScript in /App

Why? Because you don't want to mix your custom code with scripts & libraries with

Recommendation: Look at John Papa's AngularJS style guide, specifically the section on application structure

demo time, it's da bomb

SharePoint creates a new AppWeb & throws away the old one when updating the app
- Storing app data in AppWeb's lists/libraries? You'll lose it all on updates!
Handling app authentication (tokens)
- DO NOT RETURN OAUTH ACCESS TOKENS TO CLIENT
- May need an intermediary (see Research Project Code Sample in Resources section for example)

Use Google Analytics & virtual page views & custom events to track app usage
Externalize JavaScript & CSS references to a CDN
- Enables app updates without actually updating the SharePoint app
- Doesn't help with new views
Utilize A/B testing to see what UX works better for your users
- Combined with Google Analytics => killer customer service offered to your customers
Use SharePoint workflows to protect sensitive business logic
- If server-side code needed, have workflow call it... app never sees where it went / came from
Use BCS External Lists to hide where external data came from