Re:Product Design of the Stripe Dashboard for iPhone
by dsawler on Tuesday October 20, 2015 @05:15PM
(#10421857)
Hey, thanks for writing this.
Your article talks a lot about the nuances of the app (prototyping animation, specifically) but I'm curious how you were able to distill the experience down to 2 primary use cases - did this come from research, data, customers saying this is what they intend to use the app for?
Did you test any of this with your existing customers? If so, how did you go about that process?
Re:Product Design of the Stripe Dashboard for iPhone
by alphakappa on Tuesday October 20, 2015 @05:41PM
(#10422009)
If anyone from Medium is listening, here's some feedback about the page design itself. Every time I scroll, there's the 'share/follow tab' that pops in and out at the bottom of the screen. This adds undue stress to the process of scrolling when every action I do causes things to pop in and out. If a share sheet is absolutely necessary, fix it somewhere in the page, or bring it up when I come to the end of the page or something. Don't animate things as I'm scrolling the page.
Re:Product Design of the Stripe Dashboard for iPhone
by byron_fast on Tuesday October 20, 2015 @09:26PM
(#10422997)
Wow that card interface, though beautiful, looks like a real waste of time to develop. A list of text links would be faster and more effective. But mobile!
Re:Product Design of the Stripe Dashboard for iPhone
by panic on Tuesday October 20, 2015 @09:35PM
(#10423032)
A list of text links would be faster and more effective.
What makes you say that? The card interface gives a sense of context--you can still see the stuff behind it. You can pull on the entire card to navigate instead of hitting a small text target. I haven't used the UI, but it looks like it works pretty well.
Re:Product Design of the Stripe Dashboard for iPhone
by pbreit on Tuesday October 20, 2015 @10:26PM
(#10423286)
Yeah, I didn't get the card thing either. Seems too "thick" to me. The whole thing feels a little over-designed. I suspect the users may be to blame since we tend to like this crap.
Your article talks a lot about the nuances of the app (prototyping animation, specifically) but I'm curious how you were able to distill the experience down to 2 primary use cases - did this come from research, data, customers saying this is what they intend to use the app for?
Did you test any of this with your existing customers? If so, how did you go about that process?
How did you find out what the essential user experience was without talking to users?
What makes you say that? The card interface gives a sense of context--you can still see the stuff behind it. You can pull on the entire card to navigate instead of hitting a small text target. I haven't used the UI, but it looks like it works pretty well.
The card metaphor has no value. No extra information is communicated, and yet it is expensive to program and display.
UIs always look like they work well when demoed by the creator. Show me a usability test with this, and then you'll see the reality.
From what I read you guys jumped right in to the UI design?