Platform	Build	Install
Android 5.0 and up		latest release

Hunt is a virtual scavenger hunt app where players can join a game, select a team and solve hints to acquire treasure. The team with the most points wins.

The purpose of Hunt is to facilitate a virtual scavenger hunt between multiple teams. Players on each team will need to solve a riddle/hint and photograph the answer/object. If the photograph contains the correct object, the team will be awarded the full amount of points for that treasure.

For example, if the hint is "What has a neck, no head yet still wears a cap?" The teams would need to determine that the answer is a bottle and photograph a bottle. The photograph will be analyzed for the tag bottle and if it exists, the team is awarded the points.

The first team to acquire all the treasures will win the game. If no team acquires all the treasure, the team with the most points will win when the time runs out. Alternatively, the Coordinator of the game can end the game early, in which case the team with the most points will win.

https://www.youtube.com/watch?v=pXjBQD9a3AE

• Roles
  • Users can be involved in only one game at a time as either the Coordinator or a Player
    • Coordinators are responsible for
      • creating the game by configuring:
        • the amount of teams
        • the amount of players per teams
        • the amount of time the game lasts (from 5 - 180min)
      • adding treasure to the game
      • starting the game
      • ending the game early, if necessary
    • Players are responsible for
      • joining games via a 6-char entry code or scanning the QR code
      • choosing a team
      • acquring treasure once the game has started
• Treasure
  • A treasure consists of a hint and a tagged photograph supplied by the Coordinator.
  • There must be at least 2 treasures added to the game before it can be started.
  • Photos taken by the Coordinator are analyzed by
    • Computer Vision and a set of associated tags is presented, of which up to 2 can be selected. Generic treasures are acquired if the player snaps a pucture of the object and the analyzation result contains at least one of the tags assigned to the treasure.
    • Custom Vision where non-generic objects (landmarks, retail items, etc), are photographed 5 - 10 times from different angles which generates a trained model. Custom Vision treasures are acquired if the player snaps a picture of the object and the analyzation result is of .7 degree of probability of higher.
  • If teams solve the hint and take a photo of a similar object with any matching tags, the treasure is acquired.
  • As a Coordinator, when adding treasure, the hint should not give away the object - the intent is to make the players solve a riddle or puzzle and then take a photograph of the answer.

• Each ContentPage derives from BaseContentPage<T> where T is of type BaseViewModel and serves as the BindingContext.
• All outbound requests are routed as new tasks through TaskRunner.RunProtected to handle common failure scenarios such as device network connectivity changes, back-end server outages, etc.
• Game document writes are further routed through ViewModel.SaveGameSafe proxy method to handle version conflicts resiliently with minimal code.
• Most images/icons are SVG files embedded in the Hunt.Mobile.Common project assembly once and rendered at runtime via the custom SvgImage control. Fill color and vector scale can be specified per instance.
• Animations are made possible with the Lottie Animation library from the folks at Airbnb. Animations are also vector and stored in a small .json file.
• Almost all UI code is shared, include the custom HUD and Toast elements.
• The Forms navigation stack is utlizied, however, every page has SetHasNavigationBar set to false. A custom NavigationToolbar is used instead to better control the UI.
• Content for each page is declared in XAML under the BaseContentPage.RootContent node instead of the typical BaseContentPage.Content so HUD and Toast can appear at a greater Z-index.
• Supports iOS, Android, Phone, Tablet, Landscape, Portrait

• Games are saved as documents in DocumentDB. Games contain the teams, players, treasures and acquired treasures in a single document. Whenever the game is updated, players of the game are notified via silent push notification which triggers a game refresh.
• Version conflicts are raised if the associated document timestamp is out of order - it is up to the client to handle this exception and resolve the conflict. See ViewModel.SaveGameSafe.
• All images are stored in blob storage and passed to the Computer Vision or Custom Vision via the blob URL.
• Event Hubs are used to broadcast real-time, low-latency streaming telemtry on the actions that take place during a game, including any exceptions that might occur. It also serves as a way to keep track of the sequence of transactions executed for a specific game. Ingress happens on the back-end and a terminal app is provided to egress that data - both consumer and publisher utilize the AMQP protocol (this requires a constant open socket).

• Front-end

  • Xamarin.Forms
  • App Center
    • Build
    • Test
    • Analytics
    • Crashes
    • Distribution
  • 3rd Party SDKs
    • SkiaSharp (vector and SVG render kit)
    • Lottie (animations)
    • PullToRefreshPage (pull to refresh on non-ListView pages)
    • ImageCircle (better than a square)
    • CrossMedia (capturing camera photos)
    • CrossConnectivity (determining device network connectivity)
    • ZXing (QR code generation/scanning)
    • XFGloss (styled switches and sliders, background gradient)

• Back-end

  • Functions (C#)
  • Cosmos: Document DB
  • Blob Storage
  • Event Hubs
  • Application Insights
  • Notification Hubs
  • Cognitive Services
    • Custom Vision
    • Computer Vision
    • Content Moderator
  • Service Bus (timed brokered message to end games)
  • Unit tested on commit
  • Deployment via ARM Templates
  • Azure CDN

• Planning and Build

  • VSTS Work item tracking
  • VSTS Code repository
  • VSTS Build for backend + unit testing

Hunt was designed and is intended specifically for use with audiences at presentations, hackathons, community meetups, on-site meetings and speaking engagements.

To add some fun to a presentation, one option is to engage the audience in a quick game of hunt. Prior to the presentation, plant 2 or 3 well-known objects in the room somewhere inconspicuous, like a Coke bottle and a sneaker. Begin the talk by asking the audience if they want to play a game.

Display http://aka.ms/hunt on a projector and invite people to download the app. As you give an overview of Hunt, project your phone's screen so everyone can see (Reflector is a good option here as it can broadcast multiple screens simultaneously across iOS and Android using Apple Airplay or Google Chromecast). Create a quick 10-15min game seeded with some players and treasures. Then share the game alphanumeric entry and QR code so participants can join a team.

Start the game and let the teams attempt to find the objects and acquire the treasure. Consider rewarding the winning team with free Azure credit.].

• If you do not have your own Gravatar account, you can use one of a dozen Game of Thrones characters by entering their firstname@hbo.com (i.e. arya@hbo.com)
  • supported accounts: ned, sansa, arya, jon, joffrey, cersei, jamie, theon, yara, euron, etc
• When creating a new game, the mobile app has several options for seeding data into an empty game. The following options are available and allow the game to be put into different states depending on the goal of the demo.
  • User can choose to be the Coordinator or a Player
    • if coordinator is chosen, the user can add additional treasure and manully start the game
    • if player is chosen, the user is put on House Stark and the game will be started automatically
  • Games can be seeded with players that join teams - about half the game slots will fill with random mock players
  • Games can be seeded with 3 pre-configured treasures (bottle, shoe, dog)
  • If both players and treasures are seeded, the team the player joins can be seeded with 2 acquired treasure so it only takes one more acqusition to end the game.

To make it easy for new developers to stand up their own personal Hunt backend, ARM templates are used so that by clicking a button and selecting a few options (like subscription, resource group and region), developers can deploy their own pre-configured instance of all services needed by Hunt to function.