Classes

BECategory represents the category to which a specific point of interest is attributed to. The point of interest on the map is required to belong to the category in order to display map icons and have category-specific features.

BEFloor represents a physical floor object in your BESite. A BESite can have more than one floor. You can add and configure your floors on beCo Dashboard.

A BEPoint object defines any point of interest that needs to be displayed on a BEView. A point of interest can be anything from a general point, room, store, etc. You can categorize a BEPoint using BECategory.

This is an abstract class which defines the base session methods. You can access your BESDKSession from BeCo class. BESDKSession has autherisationStatus which checks that your Server API Key is authorized or not.

The BESite object defines a site object that needs to be displayed and navigated on. The BESite should be added and approved previously on the beCo Dashboard. Once you have access to the organization’s Server API Key, you can collect all sites listed using beCoMap SDK.

BELocation represents an actual cordinate point. Used to represent the lication for a site.

You use this class as-is to display map information from your application. When you initialize a map view, you specify the BESite for that map to display by calling the setSite() function. The SDK makes the initial BEFloor and floor region visible based on the user’s current location or default map settings. In addition to this, BEView supports many standard user interactions for changing the position and zoom level of the map. In particular, map views support swipe and pinch gestures for scrolling around the map and zooming in and out. BEView also provides a floor switch button that enables the functionality to switch between floors.

BeCo is a singleton class which interacts as the base interface. You can fetch your BeCo instance using function sharedInstance().