QA on expo-cli@1.1.0-alpha.1

[tcdavis]

What did I test on?

• iOS Simulator
• iOS device
• chrome
• OSX

What did you test?

• onboarding
• online / offline
• sending the link to my phone
• publishing my project
• developing snack app

Did I experience any bugs?

• the entire page would go completely black after a while. restarting expo appeared to fix
  

• there was no indication I was offline when I disabled wifi

Did I experience any confusion?

• I didn't understand the command was just expo at first. Would be nice to get a name such that npm i -g $NAME && $NAME does something (unless the idea is exp just gets updated to this)
• When I first get to the page there isn't a call to action. For snack, getting the experience running on the device or simulator is a very important moment, and I suspect this will work similarly.
• It's not clear who I'm publishing as

Do I have any nits?

• I think I defaulted to a tunnel connection
• the simulator buttons launched a toast that just hangs around regardless of what happens with the attempt
  
  this wasn't great for android (didn't work) or if I already had the simulator open (it updates but I didn't know to go look for it
• since we only display the number of panes you can fill with unique content, prefill them or add some text for drag & drop discovery?
• the publish modal was a little hard to escape. I expected escape and clicking on one of the logs to take me back. Some indication that "Publish to expo.io" is selected would be nice
• SMS is great for new users but pretty clunky once I have the app. Steering people towards "Recently in development" seems better

Things I missed from XDE

• clearing logs: I debug with liberal use of console.log, and having a way to wipe the logs so I can easily look at just the logs from this execution / since some action is super useful
• toggling dev/prod

What are your thoughts?

• This is really slick :) and probably the best handling of logs we've produced
• switching tunnel / lan is really nice and fast
• Snack is a pretty weird use case, but having this and snack both in browser was a more challenging adjustment than I expected. I'll probably end up opening this in a different browser than my default so I can get Tab cycling back
• Aside from that and log clearing it felt pretty nice to develop with
• I think I'd want to see who I am and maybe what build channel I'm targeting before I'd switch to publishing

[fson]

Thanks for all the feedback. Almost everything has been addressed now. ❤️

there was no indication I was offline when I disabled wifi

Moved this to a separate issue: #11

When I first get to the page there isn't a call to action. For snack, getting the experience running on the device or simulator is a very important moment, and I suspect this will work similarly.

#14