About the tester and use case
One important note for this log: This was done during the preview phase. We'll do a more thorough review once it's mainstream.
Quick and simple: I've used VSCode for years and I've used Github for years. I've never used Codespaces prior to this log.
Friction Logs
Friction Container boot time
Containers never boot up within the time limit threshold therefore it times out. I had to continually refresh a few times until it works. Sometimes you have to leave and come back or worse delete the code space, to get it to eventually work.
This is in preview though so it's understandable.
Friction Setting sync doesn't work
You're able to sync your VSCode settings with Codespaces. It's really nice! However, they don't seem to persist across sessions.
Friction iPad Magic Keyboard
The iPad magic keyboard doesn’t always scroll the window panes properly. Sometimes the arrows don't seem to work too.
Friction Codespaces in the desktop version of VSCode
Codespaces don't show up in VSCode desktop app. There's an extension for it. The extension allows you to create a codespace. But it says something about Azure and a few other things which make it seem like it's something else.
Delight Magical
Grabbing a NextJS app from our repo, opening it up, and previewing it while developing on it works really well.
Delight Open from a repo
Jumping into a codespace from a repo is a dream.
Delight VSCode on an iPad!
It’s VSCode top to bottom and using it on an iPad feels special.
Friction Time to use is long
It takes a good amount of time to get a codespace spun up.
Sign up and get the latest friction log studies, blog articles and podcast updates