MobileCaddy App Container Update

MobileCaddy apps run within a container which we call the “App Container”. This is the native application that your users install onto their devices from the App Store, Play Store or through your MDM solution. Our App Containers allow you to take advantage of the native capabilities of your user’s devices when writing hybrid Mobile Applications using tools such as Ionic and Angular. They also provide all of the tools needed for authentication and secure encrypted data storage.

Over the past years, we have continued to update and improve our App Containers to increase security, add features, fix issues, and maintain compatibility with the Salesforce platform. This post discusses an upcoming update we are planning to release which will mark the next stage and evolution of our mobile App Containers.

Why is this update needed?

Our App Containers use a variety of technologies such as Cordova and the Salesforce Mobile SDK (for our iOS and Android App Containers) and must also conform to the guidelines and requirements set out by the policies set out by the OS Manufacturer’s stores. Towards the end of 2017 and throughout 2018, we realised that our current tech stack for the App Containers needed an overhaul to keep us secure, robust, up-to-date, and compliant. This meant moving faster than we can by using the Salesforce Mobile SDK. We needed our own Mobile SDK.

We are focusing on security and stability with the new App Containers with the aim to cause minimal impact to your existing Mobile Application codebase.

These changes will allow us to more rapidly test and target the latest versions of our dependencies to make sure that we can review and consume security and performance updates at a greater pace. With this comes some breaking changes for us (that will not affect your existing apps) and the need to create new solutions and technologies to provide the same App Container experience that you are used to. Architecture and proof-of-concept work began in late 2018 and is currently in progress.

What is the timeline for this update?

The rest of this article will give you an overview of the current status. Please keep in mind that any timelines are not fixed and we can not give an exact or estimate release date until closer to release. Items in each phase in the diagram below are not equal and may take varying amounts of time depending on their focus. We will endeavour to update the diagram below when new phases are completed and update this page when new information is available.

App Container Update

As we get closer to testing and release, we hope to release more information regarding this update along with guidelines for any impact this may have to existing or in-development mobile applications.

Status Updates

This section will be updated as the project progresses or to notify of any changes.

Update 9th September 2019

The project is on track and is progressing as expected. As planned in the previous update, the project has reached an internal “Beta 1″ status. This will now be evaluated, and work will begin on items scheduled for the second Beta and also feedback from Beta 1. Testing of the integration work from last month is expected to be carried out in the coming month along with Beta 2 work.

Core MobileCaddy SDK:

  • Internal Beta 1 status reached – evaluation to begin
  • Beta 2 tasks have been scheduled and are under development

MobileCaddy SDK Integrations:

  • Integrations work completed and now under testing

Update 10th August 2019

The project is on track and is progressing as expected. Some exciting and important technical milestones have been passed this month:

Core MobileCaddy SDK:

  • First complete flow from install to completed initial sync successful. This milestone bring together work from across all areas of the SDK from authentication to the encrypted storage.
  • Internal Beta 1 has been targeted for next month.

MobileCaddy SDK Integrations:

  • Work is currently in progress for the integration of the MobileCaddy SDK with the MobileCaddy Salesforce package – the specification has been agreed and is currently under development.

Read more