Mobile Essentials iOS Architecture

Flashcards about the Backbase Mobile Essentials and iOS Architecture lecture.

What is Backbase?

An omnichannel banking platform that consolidates banking services under a single layer, exposing a REST API for client communication, accelerating the release of banking applications.

What are the advantages of building apps with the latest Journeys architecture?

OOTB working user Journeys, fully upgradable Journeys, project implementation only consists of styling and configurations, reduced learning curve, adherence to platform standards, not restrictive for custom build, faster market release, smaller project implementations, neobank competitive, and more agile product.

Which concepts are no longer relevant with the journey's architecture?

Widgets are replaced by journeys, Experience Manager and the model have been removed, remote navigation configuration and page structure are not used, pub's app navigation method is replaced with industry defaults, mobile SDK rendering capabilities are not used, and technical extension of BB widgets is not allowed (but product extension is allowed).

What is the ADOPT strategy for using Backbase?

Adopting a pre-configured productized application with pre-configured journeys and styling, then theming it to match bank styling and applying configurations to match specific requirements for the fastest time to market.

What are the two variations of the EXTEND product strategy?

Replacing a screen of a journey with a custom one. and building custom journeys from scratch while adhering to the navigation pattern.

What are the responsibilities of the customer application (project implementation) layer?

Custom configuration, application styling, and possibly any custom-built journeys.

What are the responsibilities of productized apps?

Default configuration, application navigation (bottom tabs menu or a left menu), session management, and platform integration.

What is the responsibility of the Mobile SDK?

Networking and security.

What is the responsibility of the Identity SDK?

All kinds of authentication, including credentials, biometrics, one-time password, or passcode authentication.

What are Journeys?

Pre-built, focused, comprehensive, and flexible building blocks aimed to provide a smooth user experience; a combination of screens and actions that the user passes through to perform a task.

What are the characteristics of Journeys?

Focused on one specific banking domain, comprehensive encompassing the entire user interaction flow and flexible with variety of configuration options.

What are the two levels of routing in Journeys?

Internal routing (screen-to-screen transitions) and external routing (project dependent).

What comprises the anatomy of a journey?

Any number of connected screens, each with its view layer and business logic, connected via an internal router. Journeys expose a public API for configurations and connect to other journeys via external routing.

What is the Mobile SDK responsible for in networking?

Handling all REST HTTP calls to send and fetch data from the backend, utilizing native mechanisms for iOS and Android.

What kind of storage does Mobile SDK provide?

In memory, persistent on the device or inside the encrypted storage.

What security feature does the Mobile SDK provide?

Mobile SDK provides encrypted storage, root detection mechanisms, asset fingerprinting, application configuration encryption, and protection against man-in-the-middle attacks using domain whitelisting and SSL pinning.

What are the main goals of the Mobile Design System?

To create multiple mobile applications that have a unique look and feel, provide a tailored user experience, and ensure consistent design and user experience across user-facing channels.

What are the key concepts in the atomic design principles?

Atoms (smallest components), molecules (groups of atoms), organisms (complex UI components), templates (pages without real content), and pages (specific instances of templates with real content).

Name the component levels in the atomic design.

Atoms, Molecules, Organisms, Template pages and Pages.

What does the design teams create for web and mobile applications?

Shared resources at the atom and molecule level.