Keep It Simple Storage

Client
The American Storage South project required the creation of an integrated system for self-storage facility management and virtual assistance, along with smart locks opening via an NFC reader. The facilities are located in Harrisburg and Concord, North Carolina.

Problem
The client came to us with the need for a white-labeled solution for facilities management – creating units, assigning locks, renting and leasing units, payments, and billing. After a few weeks of the design phase, we created a full set of mockups of the first version of the app and a technical architecture consisting of the following modules:

1. A backend API facilitating the connection of mobile apps to three major self-storage platforms: SiteLink, StoreEdge, and Ready Steady Storage.
2. A mobile application for clients to rent units, move in and out, send rent payments, and open storage locks.
3. A mobile application designed to allow facility managers to set up locks and units and check if the units are paid on time. This included the lock management module, enabling facility operators to oversee physical NFC locks.
4. A web app with a security camera module to manage cameras, video stream, and detect moving objects. A user management module to see what users are renting what units, manage support requests, and see when payments are due.
5. A video call module allowed the company to replace seven employees with one by having a large screen in each of the facilities and a virtual assistant.
6. A statistics module that gets all the info on units, virtual assistant sessions, payments, support requests, and other metrics of the system.

Solution
At the beginning of the project, the client had a web version of the app developed by another company. It was an early development version that wasn’t intended for use in production, we reverse-engineered the code structure and found out how it worked with third-party APIs.

Our first goal was to establish a link between the app with the SiteLink API to allow for the sending and receiving of information regarding payments and unit bookings. However, we encountered a lot of problems with the lack of API documentation and the app’s inability to work with individual clients.

After the SiteLink integration was completed, we started to work on the video call service for facility managers and onsite clients. We needed to make sure these calls were user-friendly and productive by making the remote assistance as helpful as possible. The manager side of the project evolved into the creation of a camera management system to monitor visual feeds in addition to the virtual assistant services.

The fourth milestone involved working on the NFC locks and implementing an NFC reader into the app, registering locks in the system, configuring them through an admin panel, and building a function for overseeing all operations via the admin panel and facility manager app.

The first challenge we encountered was integrating the SiteLink API as their documentation lacked info on crucial features. Their methods were not documented well enough, some of them didn’t have any documentation at all, which led to hours of communication with SiteLink’s support and us updating their API methods and docs.
There was also an issue with the number of requests being sent to the SiteLink API. Sending and receiving large amounts of data like payment records resulted in errors and poor app performance. This required a lot of backend optimization and the need to implement the caching of requests to reduce the workload on the SiteLink end.

Upon completing the integration of the SiteLink Mobile Backend our focus shifted to integrating StoreEDGE, which is another facility management solution. We had to navigate the complexities of connecting the mobile app with two facility management systems using our backend as a hub for restructuring requests. To address this we introduced a bridge solution between our API and the third-party application. This enabled our API to maintain its desired structure regardless of whether SiteLink or StoreEDGE (or later Ready Steady Storage) was involved in the requests. This approach led to updates in the app to accommodate differences between the SiteLink and StoreEDGE data.

To ensure compatibility across all platforms, we chose a browser-based solution. We leveraged TokBox (Vonage) and WebSockets for video calls and wrapped them into our own JavaScript app to help with statistics and the creation of a waiting room. To resolve difficulties with Tokbox’s asynchronous behavior, we implemented a series of health checks, YouTube-like stream quality adjustment, and a manual call repair to reduce downtime and call interruptions.

We introduced S3 Object storage and data security techniques like stream encryption and key management to save and store video call records from TokBox. As a result, the video call feature evolved into a separate admin panel empowering administrators to grant permissions to managers.

The next significant step was the development of white label functionality allowing other self-storage companies to use the application under their own brand. We made two major changes in the app to create this feature.

The entire backend data structure was modified to introduce a “company” entity. Facilities, users, and units were linked to the company. A New Super Admin role for KISS solution employees was added to the Role-Based Access Control and the white-labeled company employees became admins. The mobile app was made to allow customization by admins i.e. addition of their logos, colors, and other branding. Renters could now select their desired storage company from within the application.
The company managers can now share links to download the app, ensuring a transition to a customized version of the app that reflects the company’s identity while also following Google Play and AppStore’s guidelines.

Another part of the project was integrating the Rhombus camera API to create a video wall displaying camera feeds. The backend operations needed to address issues like feed stability, network performance, false alarms in motion detection, and unexpected changes in 3rd party libraries.
The last significant aspect was developing a lock management app that works via NFC. We created a new mobile app for facility managers and added the Lock/Unlock and share unit access functionality to the renter’s mobile app. This function literally allows users to walk up to their prepaid storage facility and, with a single tap of a fortified lock assembly, gain access to the facility. ONE Lock’s NFC capability allows authorized users to share facility access by simply texting an access code to a third party. This access is on a timer, which automatically revokes access after a set period of time.

Results
All sub-projects were successfully completed and bugs and usability issues quickly ironed out. A technical aspect that may require future improvements relates to the project architecture. Instead of splitting the project into two monolithic services, it may be worthwhile to explore one of two main approaches: consolidating the entire project into a single monolith or implementing a microservice-based architecture. The latter approach offers better reliability and scalability, at the cost of a longer implementation period.

However, the current architecture was shaped by factors such as limited information about the future plans for the project and changes in business requirements. The decisions made reflect a balanced approach that prioritizes code quality while still meeting the practical requirements of the project.