Odyssey OLB ReactJS Responsive Prototype 6 - Alerts

 

CHALLENGE OBJECTIVES

• Build the Alerts pages 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

• ReactJS 16

• Redux

• Bootstrap

• HTML5

• CSS3

• Material UI for icons / form validator / etc.

• Axios for API integration

• Typescript

• JSON

• Router

 

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.

 

SCREEN SUPPORT

The output of this challenge must work on desktop, tablet, and mobile phone screens, i.e. it must be fully responsive on all the required screens. For mobile screen support, you can reference the mobile app design.

 

NOTE this is the MAJOR requirement of this challenge.

 

SCREEN REQUIREMENTS

This challenge will implement all the Alerts screens in the provided design, here are some notes on some of the screens:

• The user gets to the Manage Alerts dashboard (screen 2) by clicking on the Manage alerts menu on the My Profile popup (screen 3)

• View Alert Demo (screen 5) will show a different video for demonstration purpose (i.e. do not use the same video as Online Banking Demo)

• Clicking on any of the button inside the Account Alerts, Payment Alerts, Alert History tiles will navigate to screen 7. Please based on the alerts enabled the text in the buttons should change.

• Clicking Alert FAQ will navigate to screen 6

• From screen 7 to 36 you can see how to:

  • Update account alert settings

  • Payment alert settings

  • View alert history

• Please update the prototype header to match the latest design

• This challenge should cover all the screens from the provided marvel app

 

GENERAL REQUIREMENTS

• Must use ReactJS and follow the provided design.

• This prototype must be fully responsive, meaning it should work on desktop, tablet, and mobile browsers.

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

• Searching/filtering should work whenever applicable.

• Pagination should work whenever applicable.

• Implement popup for confirmation and warning messages. Do NOT use browser alerts, but use custom styles popups as shown in the design

• Implement validation errors (for example, login error as shown in design)

• No linting errors

• 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 submission.

 

CODE REQUIREMENTS

• Following the same coding standards as the existing code.

• Use .tsx extension for React components; using PascalCase for filenames. E.g., ComponentName/index.tsx.

• Do not create a single .css/.scss file for the whole app. Each component should have its own stylesheet file.

• Ensure that there are no lint errors.

• You’re free to choose between CSS & SCSS but you need to use flex instead of float.

• 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

• Windows: IE 11+, Edge, Chrome latest, Firefox latest

• Mac: Safari Latest, Chrome Latest, Firefox Latest

• Tablet and mobile: Safari / Chrome on iOS and Chrome on Android

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 submission.