@okennedy @agx Yes, that's one step up from "not responding" or frozen. Which is the best user experience of the following:
- Your spouse leaves without saying anything to you?
- Your spouse puts a orange circular icon on the door and then leaves?
- Your spouse says, "I'm going out to get milk" and then leaves?
- Your spouse says, "I'm going out to get milk and I'll be back in 20 minutes.", leaves, and comes back in 20 minutes?
@adam @agx I completely agree that there are more opportunities for improvement here, and if that was your entire argument then I withdraw my objection. Your original post had a very disparaging tone that made it seem like you felt that this was moving things in the wrong direction. (It seems to me like a splash screen would be a prerequisite for a progress bar)
@okennedy @adam exactly! The whole point is to demo that we detect the app launch correctly, come up with some animation and have a rough idea when to close that thing (which is the most complicated bit). Spinners, nicer graphics, etc are yet to come. It's all divide and conquer:separate UI representation from the lower level plumbing so design and plumbing can progress.
@agx @okennedy I don't think you need fancy animations or ambiguous graphics at all. Just be flat out completely honest with the user: "I'm loading Firefox right now." That will make it very obvious and obvious is best: https://medium.com/google-design/the-obvious-ui-is-often-the-best-ui-7a25597d79fd