Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialAnna Grais
12,743 PointsExamples please?
I find it difficult to understand exactly what she means with the interface not being a solution or solution model or I don't know, I don't quite get what she means.
Can anybody come with an example that can put things in perspective? Exactly what does she mean, when she says that we design for experience?
For me, this video have kind of just been a lot of words I don't know what to do with.
2 Answers
eck
43,038 PointsWhen she says the interface is not the solution I believe what she is saying is the the interface is designed based on the solution model. The solution model being a list a requirements whose purpose has been validated by data collected from the people who will use the product.
That was a general example, so now I will give you a more specific web-based one:
You are building a landing page for an e-commerce web service. This is a marketing page for potential customers who may not have heard of your product prior to landing on the page. You want them to sign up for a free trial. So, before you start designing the web page visually, you need a solution model, what needs to be on this page? Some things that you may decide are needed are:
- An explanation of what the product is and why it is needed
- Clear language expressing that the trial account it free
- Testimonials or other social proof that this is a quality service
- A form that collects only the essential data needed to create a free account for the user. This component would be broken down so that you would know exactly which form fields would be used, since the more steps in a form the less likely it will be completed.
Now you have a basic solution model. From here the user interface designing can begin.
So, in summary of this example, the solution model is what should be included in the landing page and the interface is how it is presented to customers.
I hope this helps!
Donaghy Alexis Amachi Coila
1,955 PointsSo, we shouldn't start design/develop until we have clear the model solution
eck
43,038 PointsIn an ideal situation you would have a well researched solution model before designing or developing any interfaces. But this approach is more time consuming, and if you are starting a new project you might not have the luxury of time or data. In that case you may want to consider taking an MVP approach. This stands for Minimum Viable Product and is used to determine the validity of a project when time and manpower is limited.
Ultimately it is up to you and/or your team to decide when it is better to rapidly design and prototype a product or take a researched and methodical approach.