Challenge Summary
Round 1
For the first round provide the initial designs for the following screens:1) Account Change Request: Landing
1.1) Account Change Request: Submit New Request
2) Offset Request
2.1) Offset Request: App
3) Allocation App
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Desktop.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Round 2
For the final round provide the final designs for the following screens:1) Account Change Request: Landing
1.1) Account Change Request: Submit New Request
2) Offset Request
2.1) Offset Request: App
3) Allocation App
3.1) Allocation Templates
4) Reports: Custom Dashboards
- Important: As part of your final submission, you must update your MarvelApp link from the Checkpoint.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Project Background
The portal web application will be developed for investors and admin users to keep track of their portfolio. This tool will be used by investors to maximize the return by managing the investments and performing a SWOT analysis (Strength, weakness, opportunities, and threat) at a given point of time.
You will be working using the winning design from the 1st challenge as your main layout and style reference to complete all the remaining screens requested on this second part challenge.
Consider that we are providing some very detailed wireframes that have been developed to provide the best possible UX, so use these wireframes as your main reference and stick to them as much as possible. Avoid changing too drastic the layout presented on the wireframes. This is a key requirement for this challenge, so stick as much as possible to the provided wireframes.
Required Screens/Features
Note: Please follow the wireframes as closely as possible. We are providing the screen features description as extra guidance and understanding, but don’t stray too far away from the way the wireframes provided are laid out. Also, use the mock data in the provided materials to help know where data should be placed.
Please make sure your design includes the following screens:
1) Account Change Request: Landing
- Here we can show the selected trades upfront or hide it with the number of selections and give View link to check the selected and verified.
- Add Description again being an optional field we can hide it, in case of Reason as “Others” we will by default open up the Description field.
- On Submit it will ask for confirmation and then submit the request
- We understand the request flow as below: Submit request > Goes In Review > Approved/Rejected > Completed
- Considering the above flow we tried to simplify the listing, by diving them as Inprogress and completed request.
- Under InProgress we will list all In Review, Approved and Rejected requests.
- Click on the Status to view all the request History. We indicate Approved/Rejected with Red and Green indicator
Please use the layout and content from the page 3-5
1.1) Account Change Request: Submit New Request
- Looking at the amount of data that will load after selecting the From Account, we should have Submit New Request as a page, where the user can select the trades with larger real estate which helps to avoid errors.
- Submit New Request should be a flow with 3 step process.
- Choose From Account
- Select Trade
- Choose To Account
- We will have a fixed bottom bar with Next Button, once the user finishes his selection he can directly hit Next, which will open up the Popup to enter To, Reason and Submit the Request.
- Submit will ask for confirmation and redirect the user to the tools Home Page.
Please use the layout and content from the page 6-7
2) Offset Request
Please use the layout and content from the page 8-9
2.1) Offset Request: App
- To build similar experience we brought the accounts sidebar here where the user can choose the account and make the offset.
- We have combined the Status and Options column here by making the status itself as a button to make an offset.
- If it’s unavailable then the button will be disabled with red Unavailable label, once ready it will say Available and Enable the button
3) Allocation App
- Brokers can use this screen to monitor the status of their allocation requests, and look up historical records. They can also assign a template to trades that need to be manually allocated.
- Trades Status include Unallocated, Allocated, Partially Claimed, Claimed, and Rejected.
- Columns in the top section include: Template, Type, Status, OrderID, ClientOrderID, OriginalOrderID, Account, Exchange, B/S, Quantity, MoYr, Product, PriceType, Price, TimeInForce, P/C, Strike, ExecutionTime, TraderID, OrderTime, Expiry, OrderStatus, TemplateCreationTime
3.1) Allocation Templates
Brokers can use this screen to create a new allocation template and manage all of their templates
Please use the layout and content from the page 14-15
4) Reports: Custom Dashboards
Users can go to “Reports” to view various “public” dashboards and reports that ADMIS created for all users. They can also use the self-service feature within the app to create and manage their own “private” dashboards and reports.
The “private” dashboards and reports will be listed separately from the “public” ones.
Click on “+ New” to get to the self-service page to create a new dashboard or report.
For any reports:
- Users should be able to sort by any fields.
- Users should be able to hide/show any fields.
- Users should be able to export data to Excel and PDF.
- When hovering over a report, it should display a brief description of that report.
- Users should be able to change/save a public report as “private”.
For any dashboards:
- Users should be able to export the entire dashboard to PDF.
- When hovering over a dashboard, it should display a brief description of that report.
- Users should be able to change/save a public dashboard as “private”.
Please use the layout and content from the page 16-17
Users/Roles
- Admins: Access to all Customers/Brokers, Admin’s are responsible for uploading Research documents, support, etc.
- Direct Customers: Direct Customer usually have 1 account and do the transactions accordingly. In another scenario Direct Customers can have multi accounts for Family members, etc.
- Brokers: Brokers handle Multiple accounts for various customers
Form Factors
Please make sure your design supports these form factors:
- In-scope
- Desktop Web Browsers: 1366px width / height adjusted
- Out of scope (DO NOT DESIGN)
- Tablet portrait and landscape
- Mobile landscape
Operating Systems
Web Browsers.
Supporting Material
We are providing very detailed wireframes, you should stick to them as much as possible. We are providing Mockup Data so you can use real information in your designs.
https://drive.google.com/open?id=1gc_XPYYVWUighrx6vAoRgFpA3dwaV1jb
Please use the following branding material. Stick with these colors only, DO NOT add new colors. Follow winning design for better understanding.
https://drive.google.com/open?id=1Fof5pNH6gCy6RrFHkJwcCMf2fqZuDVOt
Please use the following design assets from the 1st challenge as your main layout and styles reference:
https://drive.google.com/open?id=1B628XoiDkWlqhfGzaMstSh7DCWwvGPjz
Final Deliverables
All original source files.
Files should be created in Adobe Photoshop and saved as a layered PSD file, Adobe Illustrator or as a layered AI file, Sketch or XD.
Marvel Prototype
We need you to upload your screens to Marvel App.
Please send your marvel app request to alexchekspir@gmail.com
You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.