Odyssey MB ReactNative Prototype 9 - Help and Marketing

 

CHALLENGE OBJECTIVES

• Build the Help and Marketing Preferences prototype

 

PROJECT BACKGROUND

• We believe that our customers have more important things to do than wrestle with complex products or spend valuable time administering their banking arrangements. We recognize that professional and personal lives often overlap and our mission is to help empower our customers to achieve their ambitions by serving all their banking needs.

• Banking customers are looking for a bank that can help them make their deal happen in an efficient, secure, fast, and flexible way as much as it can.

• We understand different people want different things from "Relationship management"

• We expect a counter-trend of “committed” relationships as customers react to digitization in our services.

• Our goal in this project is to create strong direct relationships with our customers. We want to provide everything - a blended bank, preferential banking for their family, and open to non-banking services via our digital app (Responsive Web App and Mobile Hybrid App)

 

TECHNOLOGY STACK

• React Native

• Redux

• Bootstrap

• HTML5

• CSS3

• Material UI for icons / form validator / etc.

• Axios for API integration

• Typescript

• JSON

• Router

• iOS

• Android

 

CODE QUALITY

You must take code quality into consideration, for example, you should create components for reusable UI / features instead of copying and pasting the same code everywhere. This is considered a major requirement in the scorecard during the review.

 

API INTEGRATION

We don’t have the API ready yet but please make sure you don’t hardcode any data, instead please create local JSON files and use these as data sources for the new pages. You should create local services to get data from the JSON files and properly implement state management using Redux.

 

DEVICE SUPPORT

The mobile app will need to support both phone screens (portrait mode only) and tablet screens (landscape mode only) eventually. But in this challenge, we only need to consider portrait mode on phone screens.

 

SCREEN REQUIREMENTS

This challenge will implement all the screens from the provided design which basically covers the Help and Marketing Preferences screens. Here are some notes on some of the screens:

• From the menu, click on Help & Support and you’ll enter the help sub-menus

  • FAQs: we have implemented FAQs in Manage Alerts, please try to make the component reusable if applicable

    • From the FAQs page, clicking Contact Us should navigate the user to the Contact Us screen

  • Contact Us

    • Implement the various options (Call / Secure Email) as per design

  • Regional Office

    • View on map can simply invoke the system maps app

• From the menu, click on My Profile, you’ll see Marketing preferences in the sub-menus

  • Please implement as per design

• It’s possible to trigger it from home screen as well (screen 29) (please trigger it when user clicks Apply Now on the banner image)

• This challenge will complete all the screens from the design.

 

GENERAL REQUIREMENTS

• Please check the document ReactNative-ApplicationStructuring-110920-1646.pdf carefully and follow the guidelines and requirements in the document.

• Must follow the provided design unless changes are explicitly mentioned above.

• The UI must work on all mainstream screen sizes (both iOS and Android).

• Show loading spinners when populating data from API / local JSON to UI

• Implement validation errors (for example: invalid input on login / signup screen)

• No errors with prod build

• You are expected to create a detailed README file including information on how to set up, run, and verify your application.

 

CODE REQUIREMENTS

• Follow the existing coding convention and standards in the base code.

• Ensure that there are no lint errors.

• Follow a clean folder structure.

• Create reusable components.

 

JAVASCRIPT REQUIREMENTS

• All JavaScript must not have copyright by a third party. You are encouraged to use your own scripts, or scripts that are free, publicly available, and do not have copyright statements or author recognition requirements anywhere in the code.

• Use ES6 linter for code quality

 

LICENSES & ATTRIBUTION

• Licenses to be followed in development:

  • Apache License 2.0

  • MIT License

  • Common Development and Distribution License

  • Eclipse Public License version 2.0

• Sufficient information regarding third-party assets must be present in your documentation. This includes the author, license info, and a direct link to the asset online.

 

BROWSER REQUIREMENTS

• iOS 10+ (iPhones in portrait mode only)

• Android 5+ (phones in portrait mode only)

Final Submission Guidelines

• Full code that covers all the requirements.

• A detailed README file including information on how to set up, run and verify your application.