© The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature 2022
L. Harding, L. BaylissSalesforce Platform Governance Methodhttps://doi.org/10.1007/978-1-4842-7404-0_19

19. Mobile Solutions Architecture (Phase H) Resource Base

Lee Harding1   and Lee Bayliss2
(1)
Clayton-le-Woods, UK
(2)
Clifton, UK
 

This chapter contains the resources required to govern Phase H of the Salesforce Platform Governance Method. As with all phases in this resource guide, the approach we have taken is to assemble the most relevant resources that align to the corresponding governance method. Since you’ve been working through the book and using these resources, you’ll know that although we have tried to cover all the major areas relating to this topic, as ever, conducting your own research in addition to examining the resources provided will really set you up for the dizzy heights of greatness!

Tip

You do not need to use this resource base as a strict method or process; the idea is that this will give you a good indication of what you should be taking into consideration. The expectation is that you will use this as a guide and then build upon it as you navigate the Salesforce ecosystem.

Guidelines and Best Practices

This chapter provides a collation of resources that brings together guidance and best practices available from Salesforce, as well as other resources that we have determined will be valuable. The objective is to ensure that the information provided in this section will enable you to actively contribute to the governance process in your organization or simply enhance your subject-level expertise.

We know there is an infinite number of resources available on the Web, and although some are better than others, this resource base will provide you with a good selection of resources that we recommend you review. As per all the resource base documentation in this book, providing the complete technical definition for every aspect of mobile solutions architecture is not the objective. Therefore, this resource base has been created with reference to the topics covered in the method that you will find informative and relevant. The resource base is divided into three main sections: the resources themselves and then related standards and associated tooling, and finally the supporting governance checklist.

As is the case with all the resource base chapters in this book, the links to the resources will be managed in the Salesforce Platform Governance Method GitHub account. The URL for this account is as follows: github.com/salesforceplatformgovernancemethod.

Mobile Solutions Architecture

Given that you have arrived at the resource base for mobile solutions architecture, we must assume that you have read the content in the governance method described in Chapter 9, “Mobile Solutions Architecture,” and so the table of resources that follow will help guide you in relation to the content covered in the method.

In this day and age, it goes without saying that mobile applications are important. In fact, we would go as far to say that if your business does not have a mobile presence, then there is a good chance that your business could suffer badly. So, why is this? In the advent of powerful mobile devices’ being accessible to just about everyone, the need to rely on your computer to manage your interests aside from normal work are over. The customer of today, rather than use a PC to manage affairs, wants the option to use their mobile device as their principal method of communication, maintaining a social presence, managing finances, and completing the majority, if not all, of all their online interactions.

Of course, generally, choosing to have a mobile app will depend on the type of business and the appropriateness of investing in mobile development given your user base. But for most businesses, it is crucial, in fact imperative, that you provide a mobile application that enables your consumers to interact with your products and services from anywhere at any time.

And now, the challenge we face as mobile app usage increases exponentially is to ensure that as we move to a mobile first way of life, that all our data, interactions, and downloads are secure and private. Our mobile experiences should be optimized, performant, and personalized for us in a way that makes the experience compelling, fun, and easy to use.

Salesforce is no different. For quite some time now Salesforce has been at the bleeding edge for mobile application options that enable Salesforce customers to use the power of the platform “on the go.” Whether you are in the airport, in between meetings, or at a show, you should always have the option to respond to your customers, respond to that urgent message, or close that deal.

To enable this, Salesforce provides the Salesforce mobile app. This is the mobile version of the Salesforce platform, providing you access to the desktop apps that you use to propel your business. Salesforce also provides the mobile SDK, which your development team can use to create meaningful mobile applications using your preferred framework, and for your experience sites, it offers Salesforce Mobile Publisher. All of these options for Salesforce mobile applications are provided in the following resources.

Mobile Resources

The resources in Table 19-1 will help you to understand the technical aspects of the Salesforce mobile solution architecture and give you the knowledge required to support your governance process.
Table 19-1

Mobile Resources

Artifact

GitHub Ref

Description

Developers Blog: New Mobile Services for the Micro-Moment

Mobile Micro-Moments

This resource gives insight as to why mobile apps are so important to us; the idea that we check our phones on average 150 times a day seems a lot, even by today’s standards. But it does raise a strong point, that mobile development and meaningful, beautiful applications are more important and relevant than ever before. This article discusses this topic and the micro-moment concepts as well as the available tools.

Salesforce Mobile App

Salesforce Mobile App

This resource introduces the Salesforce mobile app. The highlight is that you now have access to your Salesforce implementation via this out-of-the-box application. However, there are several limitations that need to be reviewed carefully against your overall business requirements. This may influence the mobile strategy and development framework you use to develop your mobile solution.

Salesforce Developer Centers: Mobile SDK

Mobile SDK

With the mobile SDK you can develop native applications for both Android and iOS; this is referred to as a native app. The Salesforce SDK also supports other development platforms as well, such as HTML5, hybrid apps, and React native. This resource goes into detail for each of the development options.

Trailhead: Develop with the Mobile SDK

Develop with the SDK

We have decided to offer this resource separately from the mobile SDK developer guide as this trail provides practical insight into each development option available with the SDK.

Mobile SDK Development Guide: About Native, HTML5, and Hybrid Development

Custom App Development

In Salesforce you can provide your user base a mobile experience using the Salesforce mobile app or by using a custom-developed mobile application. This resource focus on the custom application development options. Native, HTML5, or hybrid are all development options available to you via the Salesforce mobile SDK.

Salesforce Mobile Development Best Practices

SFDC Mobile Dev Best Practice

This resource highlights numerous items that you should consider when developing for the Salesforce mobile app. This is by no means an exhaustive list but serves to cover aspects that relate to developing custom pages.

Mobile Publisher

Mobile Publisher

Mobile Publisher is a feature that Salesforce provides that enables you to create a mobile app container for your branded Salesforce app or Experience Cloud site. Then Salesforce can help you to distribute the app to either the Google Play Store or Apple App Store. This resource describes exactly how this can be achieved—how to build and brand, test, and distribute your app.

Mobile Application Security

Mobile Application Security

This resource delves into the topic of mobile application security, addressing the security concerns that may need to be considered as part of your governance process. Use this resource to understand and answer questions that relate to security for mobile applications. This resource covers many topics, including authentication, mobile device management, and connected apps, and includes best practices and troubleshooting tips.

Mobile Device Management (MDM)

MDM

Mobile device management is worth a mention specifically as many organizations use MDM software to manage, monitor, and secure company-owned mobile devices. MDM software allows you to control many aspects, including the applications that can be installed and basic device configuration settings. This resource covers the prerequisites for MDM for both iOS and Andriod and other aspects of how your MDM software works with the Salesforce mobile app.

Identify Your Users and Manage Access: Send Mobile Push Notifications

Push Notifications

This resource details how Lightning platform developers can push notifications to users’ mobile devices as business events occur. There are several requirements that must be met to support push notifications. These are all detailed in this resource, along with all the requirements for iOS and Android support.

Field Service Mobile App

Field Service Mobile App

If your use case is to support a field service implementation, then this resource is for you. The Field Service mobile app supports both iOS and Android. This resource goes into all the details for field service, including all the limitations—and there are quite a few—that your solution will need to consider.

Phase H Standards

In the previous chapter, we discussed the importance of establishing and applying UX/UI design standards and principles to your Salesforce Experience Cloud site. In this chapter, we again iterate the importance of design principles; however, in this context the focus will be on mobile app design principles.

With any application, you want a design that will keep users coming back to utilize the features your app offers. Considering the mobile aspect of this rhetoric, not only does your app need to look great and reflect the business it serves to promote via branding and styling, but also it needs to be responsive and performant or users will be less likely to return to it.

Performance is a huge factor on which application developers should focus, especially in this age of business consumerism “on the go.” Let me explain what we mean by that. Let’s say you are a desktop user; chances are that you have booted up your desktop device or laptop to do some work and likely have several applications open at once, and will be switching from one app to another as you go about your business. Although application performance is a critical factor for you as well, the end user may be that be little bit more forgiving as a desktop user should there be any app delays waiting for processes to complete.

However, on a mobile device it’s more likely that the end user has opened the device to complete a specific task, and therefore if the experience is poor the level of frustration will be amplified because of this fact. So, the point we are making is that mobile application performance is probably the most critical aspect of your solution design.

Then there is the big question of which development process methodology should be used to produce your app. Let’s first consider the Salesforce mobile app. The important thing to note is that the Salesforce mobile app is developed, built, and distributed by Salesforce. This could be a big issue for organizations that want to control how apps are represented and branded in the app store. The benefits, however, include a pre-defined user interface, and it is possible to customize the Salesforce mobile app in many aspects. This makes it an attractive proposition and can enable you to deliver with speed.

However, if you develop a native app using the Salesforce mobile SDK, then you can use multiple platforms and processes to design, build, and manage your app. For example, if you create a custom app, then the following platforms are supported:
  • Native iOS

  • Native Android

  • React Native

  • Cordova-based Hybrid

  • HTML5 and JavaScript

Table 19-2 provides a comparison of the mobile architecture options available based on some of the common requirements that should be of interest.
Table 19-2

Architectural Comparison

Element

Native

HTML5

Hybrid

Graphics

Native APIs

HMTL, Canvas, SVG

HMTL, Canvas, SVG

Performance

Fastest

Fast

Moderately Fast

Look and feel

Native

Emulated

Emulated

Distribution

App store

Web

App Store

Camera

Yes

Browser dependent

Yes

Notifications

Yes

No

Yes

Contacts, calendar

Yes

No

Yes

Offline storage

Secure file system

Not Secure; shared SQL, key–value stores

Secure file system, shared SQL (through Cordova plugins)

Geolocation

Yes

Yes

Yes

Swipe

Yes

Yes

Yes

Pinch, Spread

Yes

Yes

Yes

Connectivity

Online, Offline

Mostly Online

Online, Offline

Development Skills

Swift, Objective-C, Java, Kotlin; JavaScript (React Native only)

HTML5, CSS, JavaScript

HTML5, CSS, JavaScript

Checklist

The Phase H checklist simply tracks that each step and sub-step within the phase are governed correctly and completely. Each sub-step may have several subject areas to form the complete coverage from a governance perspective.

Governance Step

Mobile Strategy and Design

Pass / Fail

Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app

 

Govern the authentication / authorization (including SSO), offline storage, and sync requirements

 

Govern the use of Salesforce mobile app declarative design

 

Mobile Security

Pass/Fail

Govern how the project has secured the mobile application and its data, including offline data encryption

 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.147.73.35