b-hive Mobile

Opening the App and the Initial Login Screen

The b-hive Mobile app opens with a login screen. This is not a standalone application. It requires corporate credentials tied to a Broadvoice b-hive Cloud PBX account. The login fields ask for a username and password, identical to the ones used for the desktop system. There is no option to create an account from within the app. Access is granted only through an existing enterprise subscription. After entering valid credentials, the app begins to sync data from the cloud PBX. This sync can take a few seconds, depending on the number of contacts and the network connection. The app then displays the main interface, which includes tabs for calls, messages, and contacts.

How the Core Features Interact with the Enterprise PBX

The app does not store any data locally. It functions as a mobile front-end to the Broadvoice b-hive cloud PBX. This means any changes made in the PBX are reflected immediately in the app, and vice versa. However, this tight integration creates a significant dependency. If the PBX server is down or the network connection is unstable, the app becomes unusable. The app also lacks offline mode. Users cannot access contacts, call logs, or messages without an active internet connection. This is a major limitation for field workers who may need to communicate in areas with poor connectivity. The app's reliance on the PBX also means that the quality of the service is entirely dependent on how well the enterprise maintains its cloud infrastructure.

Real-World Performance: What Users Are Actually Experiencing

The app contains no ads, which is expected for an enterprise tool. It also does not have any in-app purchases. The interface is clean and minimal, focusing solely on communication. However, user reports indicate significant issues. The most common complaint is poor sound quality during calls. Calls sometimes do not transfer properly from the desk phone to the mobile app. Text messages cannot be deleted. Incoming calls, including internal extension calls, get rejected. The call log is described as a disaster, and users cannot return calls directly from voicemail. These issues suggest that while the app's design is solid, its implementation has serious flaws that impact usability.

The Permissions That Make It Work: A Comprehensive List

The app requires a wide range of permissions to function. These include BLUETOOTH and BLUETOOTH_CONNECT for headset support, ACCESS_NETWORK_STATE and INTERNET for network connectivity, RECORD_AUDIO for calls, READ_CONTACTS for accessing the company directory, MODIFY_AUDIO_SETTINGS for call management, FOREGROUND_SERVICE for background operation, READ_PHONE_STATE and READ_PHONE_NUMBERS for phone integration, CAMERA for video calls, and multiple storage permissions for file sharing and media access. The app also requires READ_MEDIA_IMAGES, READ_MEDIA_AUDIO, and READ_MEDIA_VIDEO for accessing shared files. While these permissions are necessary for the app's functionality, the sheer number of them may raise privacy concerns for some users.