Prototyping with real data can be compared to building something out of LEGO blocks: Instead of working with imaginary, loose shapes, we can use existing components from the box and build something real. When we design a new function, we sometimes forget that not every user profile is complete, not all categories in the store have the same quantity of products, and not every product displays the same data. It’s also possible to design around different use case scenarios. All available data is visible, and it can be established what content may still be needed-as a result, communication with stakeholders and the development team is more effective. This way, no time is wasted trying to come up with bogus content, and mistakes that come from using invalid data will be avoided. It can be any kind of data-user photos, for example. When a new function is designed for an existing product, instead of using fictitious content, logical, relevant, and real-looking content can be displayed.
#FRAMER PROTOTYPE HOW TO#
If you want to supplement your knowledge, you can read our previous Framer articles: How to Create Stunning Interactive Prototypes, 7 Simple Microinteractions to Improve Your Prototypes Why You Should Use Framer with Real DataĪ common problem in designing or prototyping is the lack of real data. To follow this article, you should have at least a basic knowledge of Framer. A designer would only be limited by their imagination and coding skills.
If you know a bit of programming, its capabilities are virtually unlimited because it’s based on CoffeeScript-a relatively easy programming language. It can be used to design for any mobile device, from iOS to Android. Framer is one of the most powerful app prototyping tools out there.
0 kommentar(er)
