I've been spending time this week developing and testing the data management plan for teaching Scratch 2.0 and App Inventor. It's easy to gloss over this part, but I've found if you give the user experience more attention than you think you need to, it saves valuable classroom  time so you aren't distracted by too many/too complicated usernames and password issues and/or discovering platform bugs/scope limits as you try to teach. So, here's the strategy I'll use:

Scratch 2.0 clearly states on the website that it is MIT's experience that the system works best if each user has their own Scratch account (rather than sharing 1 account for an entire class). At day one, assign each user username and password, unique by trailing numeric (sepinventor1, sepinventor2 ...). I will use my teacher account to establish a "Studio", where you save and share class projects. Send a link to your studio to the class and they click on "add projects" to upload a project they created on their own account (make sure you've checked "allow anyone to add projects" in your studio). This allows the entire class to see what others are working on, as well, allows you easy access for programming questions that come up and need debugging.

App Inventor requires logging in through an active Gmail account, and was developed for many users to create projects using a single point of entry. I've set up an alternate gmail account from my main account for the SEP sessions so this way, all kids log in using the same username (the gmail account address) and password.

I did spend time having fun with both applications, too! I'm working on defining steps to export custom sprites created in Scratch (this was a BIG hit during the summer sessions) so they can be uploaded to App Inventor projects. Natively, it's very easy to upload the standard Scratch sprites into App Inventor. And exploring App Inventor further, I find designing projects within it is very similar to web designing, a different approach than Scratch uses, so glad to see we can use the basics from Scratch to storyboard animation projects as a jumping off point for more advanced designing concepts to apply using App Inventor.