Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

SmartHotel360 Demo App Mobile Apps

Play SmartHotel360 Demo App Mobile Apps
Sign in to queue


This is the third of a five part series where Robert is joined by various technical experts to review the SmartHotel360 demo app, which was used in the keynotes at Connect() last November and is available on GitHub. In this episode, James Montemagno shows us the hotel's mobile and desktop apps, built using Xamarin, that guests and business travelers can use to book rooms and smart conference rooms as well as customize room temperature and lighting settings. He also shows how the mobile app includes NFC access to you can open the door to your room using your phone!

SmartHotel360 is a fictitious smart hospitality company showcasing the future of connected travel:  

  • The heart of this application is Azure and the code is built using a microservice oriented architecture orchestrated with multiple Docker containers. 
  • The public website is where hotel guests can book a room, smart conference rooms, and even include their accompanying family travelers and their pets!
  • SmartHotel360 offers a fully-native cross-device mobile app for guests and business travelers built with Xamarin. Guests and business travelers can book rooms and smart conference rooms as well as customize room temperature and lighting settings.
  • Travelers need quick access to their rooms. We included NFC access from the SmartHotel360 traveler application and we also created a digital door application to check-in and open your room.
  • Mixed reality apps provide hotel management the ability to visualize data and review proposed changes to the hotel lobby by using both HoloLens and the latest in immersive headsets. 

Episodes in this series:




The Discussion

  • User profile image

    James, you mentioned the strength of Xamarin is the plethora of plug-ins that flesh out functionality and reduce what you have to build from scratch. Yet this project has custom MVVM and DI code, rather than using one of the many add-ins that do these. Can you comment on the decision to go this way?


  • User profile image

    @CodeGrue: Thanks for the question. When I speak plugins I usually mean abstractions of platform APIs:

    There are a lot of different routes that developers can go for MVVM and DI code. Xamarin.Forms itself has a full dependency service built right in. The team was really familiar with Autofac so they used a bit of that in the app. 

    The great part about Xamarin apps is that they are .NET apps so you can use what libraries you and your team feel comfortable with :)

  • User profile image


Add Your 2 Cents