JavaScript is disabled in your browser.
Please enable JavaScript settings in your browser to allow this website work correctly.
  • Android
  • iOS
  • Java

Customer

A Russian mobile service and content provider.

Problem

Softeq proved its competency level in the mobile software development space in several previous engagements with the customer working as a second-tier provider contributing strong UI design and mobile app implementation expertise. Engaging the company for its next project focused on mobile was an obvious choice.

The customer required a messenger to be utilized in a restricted enterprise environment by the company’s top managers. The development was originally carried out by an external service provider who failed to deliver a workable product. The client expected the new software development company to functionally improve and further enhance the messenger.

Solution

XMPP-driven, the messenger supports reliable encrypted message delivery. The same functionality was also implemented on the Client, which is not common practice for rendering message delivery and was a workaround to accommodate the server restrictions. The messenger has the following features:

  • Message transfer/delivery via reliable message delivery method
  • Message encryption
  • Fake contact messaging — possibility for a fake contact to send fake messages. To view the original message encrypted within a fake SMS, the recipient has to log into their private account

Challenge

Due to low code quality of the messaging app and poor solution architecture, Softeq’s team had to re-write it significantly.

Security

The message delivery is carried out using the asymmetric encryption (also called public key encryption) — a class of cryptographic algorithms which requires two separate keys: a secret (or private) and a public. The public key is used to encrypt plaintext or to verify a digital signature; whereas the private key is used to decrypt ciphertext or to create a digital signature.

Methodology

Since the project was focused mainly on functional improvement and further enhancement, the team employed the iterative implementation methodology.

Results

The messenger is designed to run on Android and iOS devices.

The existing Android version, which initially shut down on launching, has undergone significant improvements and now demonstrates reliable performance.

The iOS version was successfully submitted to the App Store (which had previously turned the submission down for 8 times). Later on, though, the customer removed the app from the open access, moving it to the local server.

The team continues to provide ongoing product enhancements. Adding message status indications, improving usability, tweaking the app to meet the higher iOS version requirements are scheduled for soon implementation.

How can we help you?