Maintenant il s’agit de déployer cet acteur dans un serveur hubquitus. Si vous avez suivi les instructions de la page getting started, vous devez avoir installé hubiquitus, ZMQ et bien sûr une base MongoDB. N’oubliez pas de démarrer une instance par défaut de mongo et bon courage si vous êtes sous windows

• Losanges : les applications utilisant une hAPI
• Rectangles : les acteurs
• Pastilles de couleur : dans la bordure gauche de certains acteurs, les adaptateurs inbound
• Cercles : les channels

• IHM Test : permettra de se connecter à la grappe et surtout de communiquer avec notre acteur.
• Gateway : cet acteur technique permet de recevoir une connection distante via Socket.IO, il réalise l’authentification de l’utilisateur distant à l’aide de l’acteur Auth
• Tracker : cet acteur technique permet certains échanges entre différents acteurs.
• TrackChannel : reçoit tous les notifications de changement dans la grappe gérée par le tracker.

We wanted to prove it with a simple use case: browsing a catalogue.

Just have a look

Give it a try! Fantastic experience to test by yourself

• connect your main screen to: http://istv.hubi.org/
• connect your smarphone using the 2Dcode or directly on http://is.hubi.org/

So why don’t we all play together on the Tv?…

• be developed and deployed on smartphones & tablets
• work on a limited bandwidth
• bring a fluid, interactive & immersive map
• use rich, contextual, real-time information

We wanted to tackle this issue.
Our approach: to work in collaboration with Visioglobe teams (www.visioglobe.com) to integrated Hubiquitus sdk within their mobile indoor map and navigation solution in order to propagate real-time information within a 3D map: Point of Interest status and sensor values are modified from a mobile interface, triggering a real-time modification on the 3D Map.

Just have a look…http://bit.ly/WRIjjM

the mobile interface

the 3D ipad indoor map

What we have now is a great starting point to a variety of use case: support geomarketing campaigns targeting shopping centers customers, drive passengers to new boarding gates in airports, or allow for the supervision of building by security and maintenance team.

We would love to hear from you if you see other potential applications.

Thanks to Visioglobe’s team

Hector, Jon & Eric for their efforts and enthusiasm in integrating our sdk.

The Alert Mama crew

1. By installing 10” tablets next to the fuel pumps allowing staff or customers to browse a catalogue of available products, add them to a virtual cart and order
2. By installing a 10” tablet in the petrol station shop, where the orders are received, prepared and delivered directly back to the customers in their car

What’ s the challenge?

1. Exchanging real time messages (orders) across a set of multiple devices, to run a potentially complexe ordering and delivering process
2. Using mass market, widely available and reliable devices, to reduce cost and allow rapid scaling
3. Ensuring QoS by relying only on infrastructures local in the petrol station (no distant or 3rd party services such as 3G data networks or cloud based applications)
4. Limit the number of software & hardware components to reduce set-up & maintenance costs
5. Provide total ability for local staff to manage the products’ catalogue and products’s features (eg. price, categories…)

The key to solving it!

1. Using out of the box Android 10” tablets (thank you Samsung for the quality of you products!)
2. Deploy the hubiquitus server components in a 200€ eeepc running linux connected to a wifi router, to support the real time exchanges &  products’s catalogue
3. Use a simple spreadsheet solution on the eeepc to manage the products’ portfolio stored in the MongoDB

The result? A solution being deployed and field tested across a number of countries by a major fuel companies Feeling this could also make sense for some of the projects. Let us know. We will be happy to tell you more about it!

How? by providing visitors with real time information about the waiting times of all key point of interest (POIs) of a venue (gates, shops, restaurants, toilets…). This information can be delivered to a large number screens, whether mobile, tablettes, or TVs. The information is collected and pushed to visitors’ by field teams from mobile phones. Sensors can also be installed to automatically provide updated information.

All year long we sit a few blocks away from Roland Garros. We thought this would make a nice use case for a prototype, made out of two components:

Component 1: Field teams have on their phone a simple, but yet efficient way to see the POIs congestion (great way to informe visitors look for help by the way):

They are just 2 clicks away from modifying the status:

The new status is instantly modified on a visitors’ specific interface that works multi devices (component 2). We tested it from mobile phones, tablets, and even a connected Tv (googletv in this case), making it a fantastic dynamic billboard:

Let us know if you think this use case makes any interest, how we could extend it, and if you could make use of it for some of your own projects.