July 2017: What’s New with MobileCaddy and Your Salesforce Mobile Apps

The Latest from the MobileCaddy Product Team - July 2017

One of the most exciting things about our Application Delivery Framework (ADF) is that it’s constantly growing and evolving, to allow our partners and customers to push the boundaries of what can be achieved with mobile apps on the Salesforce platform. As such, it’s vital that we help our community stay abreast of all the new MobileCaddy features and updates as they’re released.

With that in mind,  I’ve decided to record and publish my regular discussions with Paul, our CTO, Todd, our Chief Mobile Technical Architect, and Frank, our Lead Product Engineer. In these sessions we’ll be covering what’s new with MobileCaddy, and will be sharing this with you to provide a first-hand look at everything we’ve been working hard on to improve.

So what’s new with MobileCaddy this month?

Read more

How to Ensure Quicker and Easier Salesforce Mobile App Testing

Mobile app testing is a crucial phase within the development process, and throughout the lifecycle, as it has a direct impact on the eventual success or failure of the application itself. This article will detail a number of ways in which technology solutions, such as the MobileCaddy Application Delivery Framework, remove common challenges in this area for Salesforce project teams.

Code deployment validation

With the MobileCaddy Application Delivery Framework (ADF), code deployment is made simple from a developer’s perspective, thanks to the CodeFlow development environment. CodeFlow enables one-button deployment, from the developer’s local environment up to the Salesforce platform. This bundles up the application logic, UI, and much more into one simple flow.

 

deploy

 

Following this, an extremely important step in the testing is to ensure that code has deployed successfully. By using the MobileCaddy Platform Emulator, along with the browser’s development console, developers can validate the code immediately after it’s been deployed. This is beneficial because a partially failed deployment, or missing assets, will be picked up for correction before any QA or UAT processes begin.

Read more