I have quite a few blogs on Apps now. After all the reverse engineering over the past couple of weeks, everything is really simple now. Check out all these posts to get caught up:
- https://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2014/01/27/Lockdown-Apps-using-Sandboxed-Solutions.aspx
- https://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2014/01/24/SPWebProxy-response-limit-_2D00_-Increasing-It_2100_.aspx
- https://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2014/01/22/Office-and-SharePoint-App-Model-Authentication-_2D00_-Plain-and-Simple_2100_.aspx
- https://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2013/10/05/CJG-Review-of-All-SharePoint-Store-Apps-and-SPStore-Automater_2100_.aspx
All that content, yet I still get "Its too complicated". So, I decided to make a simple decision tree of the paths you can take when deciding what to do when building an "Application" for SharePoint 2013+. Here is the tree (Visio is attached):
