◀ Merged tasks: T2097.

hey hey

cool - just jump in anywhere I want? I am doing T2522 first.

Test:

{M14}

@epriestley, which tasks do you think we can drop from unbeta? Some seem fine for v2.

I'd vaguely like to resolve the major mechanics before we unbeta -- I think the major missing pieces are:

• Updates: we don't have a method for updating mocks. We've talked about some equivalent of rebounds but I'd like to try a real update process too.
• Distribution: I'm not sure where this was, but I think we talked about always surfacing mocks on the home page. Add CCs improved this, but I'm not sure we're far enough yet.
• Workflow: Some discussion in T2693, but we currently have zero workflow (e.g., state changes or even archiving), which I think might not be enough.

We also simply haven't used it all that much internally. Maybe we're missing secret sauce?

Although I'm not really sure where we should set the "Beta" bar -- I don't think we've actually unbeta'd anything since we introduced the status. The only things that I think are sort-of-too-janky-for-release right now are public views, mobile, and some of the ApplicationTransactions stuff, which are all fairly minor/easy.

I guess the worst case here is that if we had 100 users try it, I'd guess we'd get a lot of "How do I update it?", "How do I make people look at it?", "How do I accept/reject it?", and we don't have good answers for those questions right now.

My feeling is I'd like to have this and Conpherence unbeta by Phacility launch, it makes planning the site and marketing much easier. I also think both are 90% there. Specifically:

Updates
I think we should allow updating a mock until the point of the first comment / interaction. Covering the oops I didn't mean to upload that one case is the most common and we can play the rest by ear. We don't mean for these to be permanent records of perfection, otherwise designers will probably not use the tools much.

Distribution
Would like to solve this with Feed. I find Feed pretty useful at this point, it's low volume enough I don't feel overwhelmed and most things pertain to me. Later, I might want to just see Feed by Project as default, but not any priority. CCs works well in the rest of the cases.

Workflow
I would like states, not clear though that we need for unbeta. Mostly I'd prefer to unbeta and collect usage feedback before implementing any sort of review / close states. I have wanted to close out mocks as 'shipped'.

Mostly I weigh that we have a tool that's very useful to many orgs and I don't think a few debatable questions is worth holding it up. Getting feedback on actual usage should guide us well. On our usage, I think I'm really the only designer and I've been focused on PHUI and other items rather than large redesigns. After we launch SaaS it'd be nice to find some time for that again.

If you felt we should ship with states, I wouldn't object and would be happy to flush out what that means in a Phriction Doc.

One last thought…. even with a workflow in Pholio, we sort of agreed it would be optional to use anyways, so I think then we can simply add it later.