This repository serves as a public reference point, showcasing various components, examples, and recommended practices employed within the Backbase development environment. Its intended audience encompasses both internal and external developers, offering insights into Backbase's development approach, architecture, and workflow.
Building and running this project necessitates access to artifacts hosted in designated Backbase repository. Read permissions for these repositories are required.
Furthermore, the application establishes a connection with the EBP Sandbox Environment. To facilitate this connection, an API key is necessary. Instructions for obtaining this key are found here. Once obtained, the key should be integrated into the config.json file located within the application's assets directory.
- rbenv Utilizing rbenv ensures that a consistent Ruby version is employed for both your development environment and production. This simplifies upgrades and streamlines deployment processes. Follow the provided steps to install and configure rbenv:
git clone https://github.com/rbenv/rbenv.git ~/.rbenv
# for bash_profile
echo 'eval "$(~/.rbenv/bin/rbenv init - bash)"' >> ~/.bash_profile
# for Zsh
echo 'eval "$(~/.rbenv/bin/rbenv init - zsh)"' >> ~/.zshrc- The
.ruby-versionfile within the project's root directory defines the required Ruby version. Before proceeding, execute the following command to install the specified version using rbenv:
rbenv install {VERSION}- Bundler Bundler safeguards a uniform development environment for Ruby projects by managing exact gem dependencies and versions. It eliminates dependency-related issues and ensures consistency across development, staging, and production environments. To initiate dependency installation, execute:
bundle install- Artifactory credentials
Authentication for repo-art leverages the standard
.netrcfile located on your system. If this file doesn't exist, create it following the instructions here:
machine repo.backbase.com
login {username}
password {password}- Install necessary environment tools via:
bundle install- Configure the Xcode project using:
bundle exec fastlane setupThe project includes a test plan; however, Xcodegen cannot automatically include it. To integrate the test plan, follow these steps:
- Navigate to the Snapshot scheme.
- Select "Edit the scheme."
- Choose the corresponding test plan.
- Modify details as necessary.
Backbase Mobile leverages the Journey Architecture, a design pattern where isolated sets of screens, representing a typical user flow, are grouped into "journeys." This modular approach facilitates the construction and maintenance of mobile applications by compartmentalizing functionality.
For a deeper understanding of the Journey Architecture, please refer to the official Backbase documentation: guide
Each sample application resides within its dedicated branch. A comprehensive inventory of available samples is maintained in the CATALOG.md file. The repository undergoes updates with each LTS release, each iteration accompanied by a corresponding tag. This mechanism enables developers to effortlessly compare code changes within a sample by referencing its associated tag.
Developers are encouraged to contribute custom samples by adhering to the guidelines outlined in the CONTRIBUTING.md file. This document provides a roadmap for successful integration of your sample code
The Github Discussions forum serves as a platform for sample-related discourse. Users may engage in discussions, request new sample applications, and report any encountered issues.