Building a mobile app for fintech startup - Genuine Impact & Merixstudio

00:00 → 00:03

We were interested in your ability to help us to

00:03 → 00:06

find that user experience.

00:11 → 00:15

What we do at Genuine Impact is we provide financial research

00:15 → 00:18

on stocks and funds for DIY retail

00:18 → 00:21

investors like you and me.

00:21 → 00:25

What we've found is a lot of people struggle to analyze

00:25 → 00:29

and look at companies and to know how to invest their money.

00:29 → 00:32

They're not sure if they're making the right investment decisions.

00:32 → 00:34

They want a second opinion,

00:34 → 00:37

or they need help discovering what kind of investments to

00:37 → 00:40

make or how they should be investing, in fact.

00:40 → 00:41

For the everyday person,

00:41 → 00:44

it's very difficult to know where to start.

00:44 → 00:47

And even if you're given the same level of information,

00:47 → 00:50

it's very hard to know what to do with that information.

00:50 → 00:52

That's where we come in.

00:52 → 00:54

We found that we could simplify the process.

00:54 → 00:57

We could pick out the metrics and data points that really do

00:57 → 01:01

matter and have a long term impact on your investments,

01:01 → 01:04

summarize all of that, rank them,

01:04 → 01:07

put it into a comparative contextualized list,

01:07 → 01:10

and then give that information to you so that you can make

01:10 → 01:13

better, more confident decisions.

01:14 → 01:18

The user experience of the app is absolutely critical to us,

01:18 → 01:22

and it's one of the things we knew we didn't have right,

01:22 → 01:24

when we first launched our app.

01:24 → 01:28

We went out with what was an MVP for our app and that

01:28 → 01:33

helped us raise our pre seed value.

01:33 → 01:37

Now what we really needed to do was to

01:37 → 01:40

enhance the user experience, to completely overhaul it,

01:40 → 01:43

to make it pleasant to use, to make it enjoyable,

01:43 → 01:47

to make it effortless so that someone could pick it up and

01:47 → 01:49

understand what they were looking at.

01:49 → 01:51

There's a lot of financial terminology,

01:51 → 01:53

there's a lot of data to process,

01:53 → 01:55

So displaying that in a really clean,

01:55 → 01:59

precise way that doesn't put people off,

01:59 → 02:03

I think is critical to our business and critical to our success.

02:03 → 02:07

It's actually the reason why we approached Murric Studio was we

02:07 → 02:11

were interested in your ability to help us define that

02:11 → 02:12

user experience.

02:12 → 02:15

We know the data, we know what's important,

02:15 → 02:17

and we know what to display.

02:17 → 02:21

But how to display that and make it something that a person

02:21 → 02:24

can easily consume, that they can navigate

02:24 → 02:28

between, that makes sense when you give them an application.

02:28 → 02:32

That was the secret sauce that we are missing that Merix could help us with.

02:33 → 02:38

We decided to go for a cross platform approach because

02:38 → 02:40

we wanted to reduce our costs,

02:40 → 02:44

and we also wanted to make sure we are working off a single code base.

02:44 → 02:47

At such a small stage of the company,

02:47 → 02:48

there's a lot of unknowns.

02:48 → 02:51

It would be foolish to assume that you have an instant

02:51 → 02:54

market product fit on day one.

02:54 → 02:58

So by having a really flexible platform where we could say,

02:58 → 03:01

do our iPhone users love us the most?

03:01 → 03:03

Is this actually something for Android users?

03:03 → 03:06

Or really people want this deployed on a website?

03:06 → 03:09

It gives us a lot of flexibility that we can deploy

03:09 → 03:12

this anywhere with a consistent look and feel.

03:12 → 03:15

We've got much lower ongoing costs because the team can be

03:15 → 03:17

smaller and more focused.

03:17 → 03:20

We don't have to worry about having,

03:21 → 03:24

we don't have to worry about parity between the platforms

03:24 → 03:25

because it's one code base.

03:25 → 03:27

It is one platform to us.

03:27 → 03:30

It's just deployed in many different places.