Mobikasa carried out both consulting as well as a developing platform project based on the backend, which would automatically feed into a content management system of sorts. This system would create a website and an Android and iOS app for all devices. The platform was written using MySQL and hosted on Amazon Web Services. PHP was the language used.
Mobikasa collaborated with our guys here in Canada to develop this platform to help small to medium-sized engineering companies bring the efficiencies of content management, creation, and access to the day to day operations of any business.
For clients running an engineering company, we had issues where the controller wouldn’t update the exchange rates, which means it affected the content creator. If we didn’t have a means of posting that live, we would lose all the sales that occur or would gain on the sales that occurred before the information was updated by somebody else. So, how do we give power to the content creator in the business (e.g. financial services, engineering documents, etc.)?
This information is owned by the content creator, who publishes it on the backend. That’s what Mobikasa developed.
Also, whoever distributes the content is normally part of the corporate hierarchy, so my sales manager or application manager does not want to give all that information to all the application engineers—only the senior ones. Then, those documents would go to senior engineers in terms of access. So, who determines the content accessibility? That’s the programming on the backend—whether it’s a mobile platform that the person uses (iPad or iPhone) or the desktop, it will automatically show at the user’s end accordingly.
Basically, we try to put all the binders and files that exist in everybody’s offices and move them to a cloud-based platform. In small to medium-sized companies, people don’t know how to use email chains. Just because somebody is copied on something, he or she may assume that the sender is now giving the go-ahead. Emails chains become ridiculous, so we use the push notification protocol of the app to communicate more efficiently.
The entire platform is on a learning curve. We have 12 paying customers who are working with us, and we evolve this platform continuously. We have taken a year with Mobikasa and spent $150,000.
We met Mobikasa at the APP Expo in San Francisco. We selected them after interviewing two others—one in Poland, and one in India—that we were looking at working with. The one in India was a failure before Mobikasa came on board. We abandoned working with them. The one in Poland continued to help us with specialty things instead of this platform because they didn’t have the resources. It’s a quiet platform because we only want to work with 20 or 25 companies until the young blood comes to take over.