So what we're going to do now is take the designs that we've created and point them over to envision
and envision is basically a platform that allows you to rapidly prototype your designs.
So you might be thinking why on earth do we need to prototype things out.
And we have redesigns.
Why don't we just go ahead ghostwritten the X code and start building this thing.
So I believe that was a couple really really big reasons that I want to stress to you especially if
you are looking to create your own product or star.
So the first reason is it's really going to help you as a designer but more importantly as the products
owner so by rapid prototyping you're able to see the end goal the tunnel at the end and the end of the
tunnel.
And as your product should be and as it should appear without writing any code.
And what's really cool is that if you get a feel for it in your hand on a device by being prototyped
and you realize that you know maybe this isn't the right place to put this button.
This function is maybe not doesn't feel right or it's not the way it wants to be.
You can always go back to your designs swish things around and wait 15 or 20 minutes.
How in your hand envision or any other around prototyping tool and you can adjust on the fly without
having to write any code.
The second reason which is super important is it gives the feedback you go in for your product much
much quicker and much more efficiently and what I mean by that is you're getting it in the hands of
users in the hands of your target audience.
And they're going to give you some feedback which you can go ahead and just on the fly.
You're always always going to be getting feedback from your product from the day that it is an idea
on a napkin at a restaurant till the day that you either sell your product you know closed doors or
it flops you know whatever whatever it is may be could be an acquisition.
Who knows right from inception all the way to the very end.
You're always going to be getting these feedback loops and you're going to be adjusting on the fly.
And the sooner you start that process the faster you're going to be to a successful product.
So I'll give you an example a quick example.
I know a lot of companies that can skew the rapid prototyping phase or are they just kind of always
over and they don't really take a deep dive into the product and they just start writing code and start
writing code and then the first time that it's in the hands of an actual user it's already fully fresh
fleshed out it's this shiny new product that they've spent six months nine months creating without any
feedback.
And the user will look at it and say why did you do this and why did you do this.
And did you think about this and I've seen the faces of people who spent the better half of a year working
on something and they go wow that's that's a brilliant idea.
When I think of that and here's what happens.
They get stuck in a situation where they can unravel what they've been working on for the past six to
nine months even a year to accommodate something that is clearly a better idea.
All because they skipped the rapid prototyping phase and they jump straight into the code.
I see this happen all the time and they end up putting themselves in an area in a position where they're
choosing the the better of two mediocre decisions and especially if you're building your own product.
You have to start out you're going to want to find the most efficient path will save you the most time
save the most money and put you on the right track as fast as possible for product market fit.
So get the feedback loop started this really is possible really really you know go hard in the paint
house to put it go hard and pay with your rapid prototyping phase with your design phase because once
you start writing code it gets a lot harder to unwire things put them back together and make changes
on the fly.
So the rapid prototyping super important do not skip it.
It's going to be the most efficient in the long run.
What.