Plug your existing mobile apps to Hibe. It's easy and Free!!

The Hibe platform provides mobile app developers with a docking station where they can plug their mobile apps, enabling seamless communication between their user bases and other people using different apps.

This is an overview about how to plug your existing application on the Mobile Application Network (MAN) to make it talk to all or a selected group of other applications on the network.

Here are the 3 easy and simple steps to plug an existing application on the MAN.

  • 1- Register your existing users
  • 2- Broadcast content to other applications
  • 3- Consume content from other applications

1 - Registering your existing users

To register an app user on Hibe, you need to provide the following json fields to the Hibe API as follow:

"applicationId" : "id1178570784"
"name" : "Josh Adams",
"emails" : [ {""}, ... ]
"phones" : [ {"650-871-8874"}, ... ]

The server will return a userToken that will identify your user on Hibe.

"response" : "ok"
"userToken" : "9299123jasdas8d832hhasdhshd"

You can register more than one user in a single call. In this case, you will need to send a json array object of users. The server will also return a list of corresponding userToken for each registered user.

2 - Pushing content to other applications

You can publish any content type and combination of content including text, image, document, links and video.

If you want your content to be only available to selected applications, you can do that by specifying a list of application tokens.

You can decide which other applications you want your application to exchange content with, or simply deny this privilege, by specifying a list of application tokens. If, you exclude selected applications, these apps will never send or receive content with your app.

You can find more details on how to exchange any type of content in the documentation of the Hibe API.

3 - Consuming content from other applications

If your application is active on the Hibe MAN, the Hibe server will "push" any available content targeting a user of your application on either your app server. Then you can decide either to consumer the content available for your app users on your ouwn server or let the user app on their devices to consume it directly. In the latter case, this means you don't have to change anything in your existing data structure.

You can also periodically pull a list of content available for users on your application, your application call call the API below:

By default, your application will accept any type of content. It will be up to your application to present them or not to the end user. If you want your application to receive only accept specific type of content from other applications, you can do so.