Challenge Overview
CHALLENGE OBJECTIVES
-
Build the UI prototype for the security and dashboard modules using React JS.
-
This is part 2 of the prototype and we have a lot more to come soon.
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
In the previous challenge, we only implemented a very basic dashboard page and it only supports desktop resolution, in this challenge we need to implement more dashboard design and make the prototype fully responsive.
The output of this challenge must work on desktop, tablet, and mobile phone screens.
NOTE this is the MAJOR requirement of this challenge.
The desktop prototype must work on screens with 1280px width and above.
SCREEN REQUIREMENTS
-
Responsiveness
-
The current prototype already supports desktop screen resolutions down to 1280px
-
Please update the prototype so it works with tablet screen resolutions, check the design in the forum to see how the screens should look like under 1024px
-
Please update the prototype to work with mobile phone screens (portrait mode), please check the mobile app design in the forum, even though some of the screens (like face id, touch id, etc) don’t apply to desktop, I believe there’s enough information to convert the existing desktop screens to mobile.
-
-
Dashboard
-
Keep the charts as static images for now.
-
No need to implement the Modify / Save feature for the Finance Manager section.
-
Implement the demo video as shown in D - 09 - 3
-
Implement the account, notifications, and help pop-outs
-
For My profile, the Manage my account link can be a static link for now
-
For Notifications, View all messages can be a static link for now. However all the notifications should be coming from json, and the different filters should work.
-
For Need Help, both FAQs and Knowledge base links can be static for now
-
-
The side menu should be expandable / collapsible
-
Implement the no activity detection as shown in D - 03 - 8a and D - 03 - 8b
-
-
Other screens
-
Any other screens not mentioned above are out of the scope of this challenge
-
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
-
ES6 syntax is preferred, as Babel has been set up to handle transpiling the syntax to the current JavaScript standard.
-
Use .jsx extension for React components; using PascalCase for filenames. E.g., ComponentName/index.jsx.
-
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
FINAL DELIVERABLES
-
Full code that covers all the requirements.
-
A detailed README file including information on how to set up, run, and verify your submission.