So many applications now offer some form of real-time UX and real-time functionality is becoming increasingly essential as technology trends evolve. Notifications and activity streams in Facebook, Twitter, news and sports apps; real-time location tracking in Uber and most other taxi (logistics) apps; real-time collaboration in Google Docs and Microsoft Office 365 online. What sort of experience would chat apps like Slack, HipChat, WhatsApp, Viber or WeChat offer if messaging weren’t instantaneous? And you can be sure that bots will be powered by real-time technologies.
So, in order to meet user expectations and deliver innovative solutions that align with technology trends, you’re going to need to make use of real-time technologies.
If you build your apps using a .NET stack and you want to add real-time communications functionality to a .NET web app, what considerations should you take into account when choosing a real-time solution? What .NET frameworks or solutions exist? Should you restrict yourself to .NET? If not, how do you integrate with another technology?
I recently gave a talk on Real-Time Web Apps & .NET at DevWeek in order to address all of these questions. I cover why real-time matters, the common uses cases for this technology, the common real-time communication patterns you’ll find in solutions and which patterns map best to each use case. We’ll apply each pattern when building an ASP.NET MVC chat application using SignalR, XSockets and a hosted service.
It’s a 90 minutes talk so if you’d prefer to skip through the slides you can find them here.
Please get in touch on twitter (I’m @leggetter) to let me know what you think.