iOS Essentials for Journeys Flashcards

Flashcards covering key concepts from the iOS Essentials for Journeys course, focusing on custom business logic, Use Cases, and screen replacement.

What is the intent of Section 5: iOS Essentials for Journeys (Build strategy)?

To familiarize iOS developers with replacing the default business logic of a journey with a custom one in the Backbase productized application.

What can custom business logic include?

Custom API calls, data validation, and more.

What are the components of a Backbase Journey?

User Interface, View Model, Use Case, Client

What object is responsible for performing network calls in a Backbase project?

The Use Case.

What does swapping the out-of-the-box Use Case with a custom Use Case accomplish?

Use a different, custom-built client to perform network calls and apply custom business logic to shape and manipulate data as needed.

What protocol does FakeTransactionsUseCase conform to?

TransactionsUseCase

Why are mappers required?

To convert TransactionItem to RetailAccountsAndTransactionsJourney.Transaction.Item.

How do you write a custom Use Case?

Find the protocol for the Use Case that you want to replace and then conform your custom Use Case to that protocol by implementing the appropriate methods.

Where do you register your custom use case with Resolver?

In the AppDelegate

What is the aim of the Mobile Essentials iOS - Replacing a Screen in a Journey course?

To become familiar with replacing the default journey screens with custom ones in the Backbase productized application.

What are we going to do in the Mobile Essentials iOS - Replacing a Screen in a Journey course?

Create a custom screen that uses the default client.