fertroute.blogg.se

Flinto examples
Flinto examples












flinto examples

I personally try to get to HTML/CSS/Javascript based mockup’s- stuff that works but isn’t necessarily talking to a real back end. On step 05, there are folks who will test paper prototypes or static mockup’s. It’s a great idea to draft up at least two approaches- if nothing else it will help get you thinking in terms of alternatives which is how things work in this area. Steps 03-04 depend a lot on your environment and available resources. This is more of a Chapter 3, product design item.įor step 01, please see the related sections in the Venture Design Intro. Please Note: This is distinct from your ideation around the business overall- chapters 1 & 2 of ‘ Starting a Tech Business‘ are better resources for that. Your ideation process around product UI should probably look something like this: Over-attending to details will a) distract your audience b) likely waste your time because you’ll want to change things anyway and c) get you over-invested emotionally in your concept when you need to be most open to dramatic and fundamental change. Best of all, it’s not that hard (really truly).Īssuming you’re at the ideation stage, my advice is to keep your prototype simple. If you’re short on designer time and/or pay for it by the hour, getting in the habit of early prototyping will keep you from throwing good money after bad/misaligned ideas. It also shows people you’re serious and that you’ve really thought through your idea. Prototyping has a surprising power to help people understand what you mean, a power which is generally under exploited. You should err on the side of prototyping whenever you have a new product idea with a user experience component.

#FLINTO EXAMPLES HOW TO#

Sketching out a prototype is a great way to show everyone what you had in mind so that you can have a productive, directed discussion about how to iterate on possible solutions.

flinto examples

blindly delegate it to ‘the design people’ and/or the ‘developers’). If you’re (one of) the lead(s) on figuring all this out, it’s probably a good idea for you to participate in that process (vs. If you have a handle on those, you have a solid idea of what you want to do and (more importantly) why. Personas encapsulate your understanding of the customer, Problem Scenarios your opportunity, and User Stories how you’re going to deliver on the opportunities. Creating a prototype with in a mockup environment.Leveraging and matching best practice design patterns to your application.I recommend working out your Personas, Problem Scenarios and User Stories before diving into prototyping but there’s no single right approach. This post introduces the process of prototype in a practical fashion- so practical that with a little practice you can do a thoughtful prototype in 20 minutes.














Flinto examples