Challenge Summary
Welcome to Moneta - Mobile App Design Concept Challenge. Moneta is an application that give users the ability to manage and view their spending on current accounts. In this challenge we need your help to design a storyboard of this mobile application.
Round 1
Following is requirements you must submit at checkpoint round:
Savings Mode.
Round 2
All required features and feedback given at checkpoint round.
Project Overview
Moneta is a companion application for a mobile banking application. This application should have symbiotic relationship with mobile banking application. The application give users the ability to create, edit, delete and view current categories and to view/alert/understand spending on their debit cards. The idea is that users will be able to follow their money transactions and track their spending. This app will make saving money more fun through gamification.
This app will be native for iOS - so please design to maximise this.
Real time card based transactions can be delivered into the app to show customers their spending as it happens. Assume an API will be available to deliver all of the information listed. The app is primarily for tracking current acounts and planning savings.
User Scenario
The users are likely to be aged 18-35 and heavy users of their iPhone. They enjoy gadgets and use mobile apps to manage their money. They rarely visit the branch in-person or phone the bank call centre.
These are digital natives and they want information on their money quick and fast. They want to be able to do as much as possible through their phone.
Required Features
1. Savings Mode
- Allow users to visually ring fence part of their current account balance on a mobile banking app for near future spending by creating some type of ‘categories’ or ‘envelopes’.
- The spending categories should be personalised and have the ability to use a nickname, target amount, goal date.
- The ability to virtually lock the total amount of all categories funds away from a current account balance.
- The total amount of funds ‘locked away’ using this functionality will impact the balance – therefore if you have 100euro locked away for end of the month – until this is released the customer will not have this money available to spend.
- Customers should be able to withdraw from and add to each category at will but the UX will feel like there are consequences to this - make the users stop and think if it’s worth spending/moving the money.
2. Spending Mode
- As the customer uses their card in retail outlets the information is passed into the app in real time. The design can make use of this data to link transactions to categories or to remind users of future spending commitments. Possibly create a way of showing what is safe amount to spend based on the available funds.
The API for card transactions will deliver the following data to the screens:
a. Timestamp
b. Merchant Name
c. Transaction type
d. Online or POS (point of sale in a bricks and mortar store.)
e. Amount
f. Geo Location
g. Category of spend, e.g. fashion, food, service station etc. (assigned and created by the user)
Gamification
We would like to see your ideas for making saving money gamified and more engaging.
Gamification of the micro-savings and spending – help customers to become conscious of their spending and to allow for it in their balance – not to overspend but also where they are ‘breaking into’ money that’s already spent they are aware of the consequences.
User Flow
1. Check new balance with all reserved funds accounted for.
2. View, create, edit and delete categories of funds.
3. Add and remove funds from current account to categories and vice-versa.
4. View the detail information for each debit card transactions.
Branding Guidelines
- Currency is in Euro (€).
- Font and colors is up to designer.
Target Devices
iPhone 6 Retina Display 750x1334 px.
Target Audience
Bank customers and debit card/current account users.
Judging Criteria
- How well your solution gives the best experience for users.
- Creativity and cleanliness of your graphics and design.
- Your solution should follow the standard in building the mobile application.
Submissions & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Submit JPG/PNG for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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.