Single-Page Applications (SPAs) in SharePoint Using SPServices
Next Event
Description
Single-page applications (SPAs) are nothing new on the Web. However, like Responsive Web Design (RWD), SPAs have gained favor as a way to enable real work with an improved user experience (UX).
SPAs first started popping up regularly in creative contexts on public Web sites. Many of the early SPA sites were marketing sites: they were primarily publishing content in a one-to-many context. These sites have been out there for a while and are becoming more prevalent.
Since the idea with SPAs is that one need not leave the single page to accomplish some high percentage of the tasks at hand, it’s a great concept to apply in a SharePoint context. The days where a clunky postback-ridden application was acceptable is fading into the rear view mirror. It’s all about Getting Work Done as effectively and painlessly as possible.
We’ll look at an SPA example taken from Marc’s popular blog series on building SPAs in SharePoint and discuss successful approaches and pitfalls in doing so.