Re: [Snowdrift-design] Mockup of account history
On August 9, 2016 2:08:41 PM EDT, Aaron Wolf wrote: >On 08/09/2016 10:42 AM, Bryan Richter wrote: >> On Tue, Aug 09, 2016 at 10:09:47AM -0600, Michael Siepmann wrote: >>> On 08/09/2016 07:23 AM, Stephen Michel wrote: >>> I agree with Michael here, but there is a limit. Imagine a user who pledges to many projects which are then suspended as they grow, but who is also lazy and leaves the pledges suspended rather than dropping them. Their history could become bloated with (imo) useless information as the months run by. I think the proper place to tackle this is: if a user has not reinstated a suspended pledge within 3 (?) months, it should be automatically dropped. Apologies if we've already had this conversation; I do remember talking about it but not this particular facet, and mobile makes it hard to go back and check. >>> >>> This seems like a good idea to me. I think we should notify them >>> with some reasonable notice, e.g. a brief email 2 weeks before it >>> will be dropped. Also they'll of course have been notified when it >>> was initially auto-suspended. (In both cases they might be able to >>> opt out of these notifications, but I certainly think the default >>> should be to be notified of these situations.) >> >> Truly, this question was discussed to death some time ago. :P Sadly I >> don't recall what the outcome was. >> >> Aaron, maybe you remember? >> >> > >We never discussed anything about the situation of suspended pledges >getting eventually fully dropped. > >For notifications about suspensions, we decided that notification of >suspension itself is adequate along with a regular status-update >notification (regardless of suspension) so that people are aware of >progress overall. Mostly the decision was to have the absolutely >necessary notifications first, later add optional extra notifications, >basically iterateā¦ Seems entirely reasonable. I propose not to worry about dropping pledges until post-launch. -- Sent from my phone; please excuse my brevity. Email policy: http://smichel.me/email ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Snowdrift-design] Mockup of account history
On 08/09/2016 10:42 AM, Bryan Richter wrote: > On Tue, Aug 09, 2016 at 10:09:47AM -0600, Michael Siepmann wrote: >> On 08/09/2016 07:23 AM, Stephen Michel wrote: >> >>> >>> I agree with Michael here, but there is a limit. Imagine a user >>> who pledges to many projects which are then suspended as they >>> grow, but who is also lazy and leaves the pledges suspended >>> rather than dropping them. Their history could become bloated with >>> (imo) useless information as the months run by. >>> >>> I think the proper place to tackle this is: if a user has not >>> reinstated a suspended pledge within 3 (?) months, it should be >>> automatically dropped. Apologies if we've already had this >>> conversation; I do remember talking about it but not this >>> particular facet, and mobile makes it hard to go back and check. >> >> This seems like a good idea to me. I think we should notify them >> with some reasonable notice, e.g. a brief email 2 weeks before it >> will be dropped. Also they'll of course have been notified when it >> was initially auto-suspended. (In both cases they might be able to >> opt out of these notifications, but I certainly think the default >> should be to be notified of these situations.) > > Truly, this question was discussed to death some time ago. :P Sadly I > don't recall what the outcome was. > > Aaron, maybe you remember? > > We never discussed anything about the situation of suspended pledges getting eventually fully dropped. For notifications about suspensions, we decided that notification of suspension itself is adequate along with a regular status-update notification (regardless of suspension) so that people are aware of progress overall. Mostly the decision was to have the absolutely necessary notifications first, later add optional extra notifications, basically iterateā¦ signature.asc Description: OpenPGP digital signature ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Snowdrift-design] Mockup of account history
On Tue, Aug 09, 2016 at 10:09:47AM -0600, Michael Siepmann wrote: > On 08/09/2016 07:23 AM, Stephen Michel wrote: > > > > > I agree with Michael here, but there is a limit. Imagine a user > > who pledges to many projects which are then suspended as they > > grow, but who is also lazy and leaves the pledges suspended > > rather than dropping them. Their history could become bloated with > > (imo) useless information as the months run by. > > > > I think the proper place to tackle this is: if a user has not > > reinstated a suspended pledge within 3 (?) months, it should be > > automatically dropped. Apologies if we've already had this > > conversation; I do remember talking about it but not this > > particular facet, and mobile makes it hard to go back and check. > > This seems like a good idea to me. I think we should notify them > with some reasonable notice, e.g. a brief email 2 weeks before it > will be dropped. Also they'll of course have been notified when it > was initially auto-suspended. (In both cases they might be able to > opt out of these notifications, but I certainly think the default > should be to be notified of these situations.) Truly, this question was discussed to death some time ago. :P Sadly I don't recall what the outcome was. Aaron, maybe you remember? signature.asc Description: Digital signature ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Snowdrift-design] Mockup of account history
On 08/09/2016 07:23 AM, Stephen Michel wrote: > > I agree with Michael here, but there is a limit. Imagine a user who pledges > to many projects which are then suspended as they grow, but who is also lazy > and leaves the pledges suspended rather than dropping them. Their history > could become bloated with (imo) useless information as the months run by. > > I think the proper place to tackle this is: if a user has not reinstated a > suspended pledge within 3 (?) months, it should be automatically dropped. > Apologies if we've already had this conversation; I do remember talking about > it but not this particular facet, and mobile makes it hard to go back and > check. This seems like a good idea to me. I think we should notify them with some reasonable notice, e.g. a brief email 2 weeks before it will be dropped. Also they'll of course have been notified when it was initially auto-suspended. (In both cases they might be able to opt out of these notifications, but I certainly think the default should be to be notified of these situations.) signature.asc Description: OpenPGP digital signature ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
Re: [Snowdrift-design] Mockup of account history
On August 8, 2016 1:30:11 PM EDT, Michael Siepmann wrote: >On 08/02/2016 05:55 PM, mray wrote: >> * items that did not contribute to a months spending can be omitted >for >> clarity. Carried over pledges appear on the respective new month. >> Suspended projects are not treated different as non-pledged and >should >> not show up specially. Notifications can be used to communicate all >details. > >I strongly disagree with this. I think omitting this information >creates >lack of clarity. I think we should assume that users will rarely look >at the history, but that when they do, it's because they want to >understand where their money went (or didn't) and why. That includes >knowing that it where it did *not* go that they might have expected it >to go, e.g. to a suspended project, and knowing why they were *not* >charged that month, i.e. because balance was carried over. I agree with Michael here, but there is a limit. Imagine a user who pledges to many projects which are then suspended as they grow, but who is also lazy and leaves the pledges suspended rather than dropping them. Their history could become bloated with (imo) useless information as the months run by. I think the proper place to tackle this is: if a user has not reinstated a suspended pledge within 3 (?) months, it should be automatically dropped. Apologies if we've already had this conversation; I do remember talking about it but not this particular facet, and mobile makes it hard to go back and check. >> * I also like keeping the history tab consistent with the running >months >> matching tab. > >I do not think consistency with the main dashboard view should be a >goal >here. They have very different purposes. The purpose of the main >dashboard view is to show your limit, your current pledges, your amount >available to crowdmatch others, and especially the *relationship* >between these. This means it makes sense to use a lot of space to make >the relationship clear. In contrast, the purpose of the history is to >clearly and concisely show and explain a historical record of >transactions. A familiar format like an account statement, that makes >efficient use of space is much better here, in my view. I think having the history be consistent with the main dashboard view is desirable but less important than a clear record of transactions. -- Sent from my phone; please excuse my brevity. Email policy: http://smichel.me/email ___ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design