Somewhere in the recent emails between Stephen and Aaron (which I've looked through but not read every word of) Stephen referred to working on a mockup. I think mockups are what we really need at this point, to ground this discussion and start focusing on how to make this look straightforward enough from the user's point of view. They don't need to be complete page mockups and certainly not high-fidelity visually designed mockups. They can be rough partial wireframes to start representing proposals for the basic information and controls the user will interact with.
/Stephen:/ In what format are you making a mockup? How soon do you think we could look at it? I'm interested in trying Pencil (https://github.com/prikhi/pencil). Unfortunately the tool I have the most experience with currently is proprietary (Axure RP) and I'm eager to start exploring and learning how to use a FLO alternative. (By the way, I unfortunately have a conflict on Monday and won't be able to be at our regular meeting.) Best, Michael Michael Siepmann, Ph.D. *The Tech Design Psychologist*™ /Shaping technology to help people flourish/™ 303-835-0501 TechDesignPsych.com <http://www.TechDesignPsych.com?id=esig> OpenPGP: 6D65A4F7 <http://pool.sks-keyservers.net/pks/lookup?search=0x6D65A4F7&fingerprint=on&hash=on&op=vindex> On 05/20/2016 12:06 PM, Bryan Richter wrote: > I'm kinda... not reading too much of these right now, but there was a > question I could sorta answer: > > On Thu, May 19, 2016 at 11:12:24PM -0400, Stephen Michel wrote: >> I'm a user. I go to snowdrift.coop, log in, go somewhere (I'd assume >> dashboard, but I'm trying not to assume), and click on a button to >> add funds to my account (current balance: $0). I specify $50 and >> click 'next'. Now what happens? I presume I'm prompted to log in to >> Stripe. Am I also prompted to authorize $50 for snowdrift, or does >> that come later, or for individual transactions, or...? > This is partially dependent on the API of the payment processor. > Stripe has two options, one of which is "managed accounts". With that > option, users won't have to have their own Stripe account. I'm not > certain what the workflow for getting their payment data is, but I'm > pretty sure it involves Stripe's UI. At any rate, we'll never > see it, and it will be pretty streamlined. > > Right now there are two likely stories. They are: > > 1. The Admiral > > - User pledges to a project, and damn the torpedoes. > - If they're not logged in, they can log in, and/or create an account > - If they don't already have a managed account, it is set up > - If they don't have any funding limits set, they are asked to specify > what maximum amount of money they want to donate per month. > - The become pledged to the project. > - ... > - Monthly, their pledge(s) are processed, and they donate an amount up > to the limit they set. > > 2. The Spy > > - User holds their breath and creates an account > - User cautiously pokes around the dashboard and /how-it-works > - User feels more confident, and goes to the dashboard and chooses to > make funds available > - They set up a managed account > - They specify a maximum amount of money to donate per month > - Finally, they poke around the available projects, and pledge to one. > - ... > - Monthly, their pledge(s) are processed, and they donate an amount up > to the limit they set. > > Note: both of these are "arrears" methods. I believe they are safer > and simpler than "pay upfront" methods. Even though I prefer the > latter for a few different reasons, I'd like to stick with "safer and > simpler" for now. > > > _______________________________________________ > Design mailing list > Design@lists.snowdrift.coop > https://lists.snowdrift.coop/mailman/listinfo/design
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
