Design and Development For Mobile Banking App
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Please draw your structure.
NAMU Systems is a FinTech startup based in Poland. I am CEO and cofounder of the organisation.
What business challenge were you trying to address with Polidea?
We',re operating off the announce that mobile is the forthcoming of banking. While the superiority of banks have begun to form their own apps that allow their clients to track spending and such, we quiet felt there was a huge occasion to form a better experience for the client. Our app, NAMU, fetchs in aspects of collective media to mobile banking. Customers can add pictures and geo-location services to track their spending better as well as join collective circles of friends to hold one another responsible to making wise financial decisions. Obviously, for this type of organisation the condition of the app is tremendously significant. Although we have a few in-house developers, the size of the work necessitated that we fetch in outside help as well.
Please draw the aim of their involvement in detail.
Actually, we already had a general idea of the static design when we accessed Polidea, but we didn',t have any concept of what the UX [user experience] would be like. We began off with the branding and the design, then we went on to work with the UX and developed outgrowth of the app. Those were the two phases that Polidea took on for us.
They leading completed the iOS app and, almost two months later, we did the Android app. We were working on a firm schedule owing we wanted to have the artistic fruit in the fall of 2014 to make sure we could component the app in some of the activity',s big trade shows.
How did you come to work with Polidea?
Polidea was recommended to me by separate different friends of mine in Warsaw. After meeting with them, I was positive they could get the work done.
Could you prepare a perception of the size of this start in financial provisions?
It was almost a $100,000 project.
What was the timeline for the work?
We began in March 2014, and the app was fully completed in November 2014. We had weekly progress meetings and followed the minimum viable fruit access. We made sure to complete the core issues leading. Then, we began expanding a bit.
Could you share any statistics or metrics from this engagement?
The app has been won separate activity awards, including being named one of the top innovators at the 2015 Citi Mobile Challenge.
What was the best thing almost working Polidea in your mind?
I ponder they were very answering, I',m in Poland and have two partners based in the United States, and we never had any trouble with interaction. We didn',t have to tell them anything twice.
I ponder as clients, we were managed properly, and they allowed themselves to be managed as well. It was a very nimble relationship – intense but nimble – and I felt satisfied. We got the right mix of genius, I would say. We also accepted good advice in provisions of order: when to stop, when to add more functionality, and what the trade-offs and the risks were with the app. Lastly, it should be said that they were coding a very tricky app, and they did a beautiful job edifice a wonderful-looking app that quiet functioned well in provisions of despatch.
Is there anything Polidea could have improved or done differently?
I ponder down the line we did substantiate that some of the architecture decisions could have been better. When you',re following the lean outgrowth standard, you end up making a lot of trade-offs that pay short-term dividends, but don',t pay off long term.
When you say architecture, are you referencing the design and the code or more the project?
I ponder with these types of projects there are many things that you wish you had done differently.