Nice, Please do mail your customers later on with an offer to feature their best work using your flow cards on your website, it could improve the conversions for both! P.S. I've added FLOWCARDS to the curated list of startup tools I've been trying to build - https://startuptoolchain.com/#design , Hope that's fine.
I've designed UI Flow Cards because I couldn't find one like it
31–40 of 55 posts
Re: I've designed UI Flow Cards because I couldn't find one like it
#32Re: I've designed UI Flow Cards because I couldn't find one like it
#33Re: I've designed UI Flow Cards because I couldn't find one like it
#34So afraid they're not much use to me
Re: I've designed UI Flow Cards because I couldn't find one like it
#35These are all desktop designs whereas in consumer facing sites the majority of visitors are on mobile (at least 60% for most of my clients) So afraid they're not much use to me
Re: I've designed UI Flow Cards because I couldn't find one like it
#36Instead, I view these as basically standardized "icons" - a visual language - with each depicting a function/meaning of one page (or step) in a flow. For example, you could have a "landing page" flow card, "account login" flow card, "home dashboard" home card, depicting the user flow when accessing their account.
It doesn't matter what the actual wireframe layout is at that point, as this is for a step before that, where you want to see what are the steps the user follows to do a specific thing.
I might be completely off the mark here, but if that's the intention: preparing a smaller, well defined and named set of cards, basically designing a language for this, would be clearer. As a non-designer, mixing the semantic value of the cards (if understood as icons) and the actual layout on each of the card (a step toward wireframing) makes it more confusing. Limiting the number of choices would force the designer(s)/stakeholders to focus on the meaning, not the mechanics.
Re: I've designed UI Flow Cards because I couldn't find one like it
#37Re: I've designed UI Flow Cards because I couldn't find one like it
#38The way I - a non-designer - understand this, these flow cards are not wireframes as such, where the intention would be to structure the information/content presented to the user on a page. Instead, I view these as basically standardized "icons" - a visual language - with each depicting a function/meaning of one page (or step) in a flow. For example, you could have a "landing page" flow card, "account login" flow car…
Re: I've designed UI Flow Cards because I couldn't find one like it
#39Since I’m not a UI designer, I’m a bit lost. I’d appreciate it if someone could explain more since the website doesn’t. Why would one use this at all? And how would one create web pages conforming to the cards?
It saved so much time as we could co-design large parts of the site with them before going anywhere near a computer.
Re: I've designed UI Flow Cards because I couldn't find one like it
#40Since I’m not a UI designer, I’m a bit lost. I’d appreciate it if someone could explain more since the website doesn’t. Why would one use this at all? And how would one create web pages conforming to the cards?
I may be wrong, as I have never used them, but I think wireframes are used to Graphically design a site layout. Once a design is approved, it is then up to a UI "engineer" to translate that design into actual HTML/CSS.