This is a short doc containing a few ideas about how to license WebLogo. The ideas have not been tested at all, and some of them may not realizable.
WebLogo has a big problem: it cannot access local files.
On the positive side is that WebLogo can access Google Drive, WebDAV servers, predefined storage on the Terrapin server, and local storage.
Logo can also not print the Graphics panel, nor can it save the Graphics panel. The browser can, of course, print a screen shot, though.
Logo 4 licenses were thought to be easy to handle. Well, it cannot be easy enough, so I'd opt for a different licensing scheme.
What if we switched to a user/password login for WebLogo? When ordering WebLogo, customers enter a desired username and password. On payment, this combo is just activated.
The WebLogo main page would be a login dialog with two buttons: “Login”, and “No thanks; I'll just try it out”. Logged-in users have full access to WebLogo and more (see below), while guest users have access to a toned-down version without storage.
As before, we can limit Logo's file saving feature for unlicensed users.
To user maintenance, we have an own database; Magento can access and fill this database automatically. For school network admins, we can store additional config data, like e.g. the configuration of local school storage. For advanced admins, we could even offer a pre-packaged storage server (WebDAV) that they can install easily.
Although WebLogo can connect to several storage providers, I believe that setting up storage would be way over the head for the average teacher. Therefore, I suggest that we offer storage space on a server for registered users, and set up that storage when Logo starts. The space can be small, because Logo programs are typically small.
For multi-user licenses, we need a way to add sub-users. I do not yet have a good idea about how to implement that (a second user field? Or a scheme like main.sub?). We would probably set up standard user names for sub-users, like e.g. “challengerschools” and “user1” through “user25”. We can talk about how this would look like. Maybe we also should offer main users a way to rename sub-users. Each sub-user has his/her own storage space, and read-only access to the main user's storage, where that user could store projects or tasks.
It is tempting to offer an environment that creates programs that do not look like a Logo program. We had the Logo runtime back in version 3, we had Logo packages in Logo 4; now, we should offer Logo apps. The Scratch environment is also so popular because people can upload their projects for everyone else to run.
The WebLogo main page would have sections like “create project” or “create app”, where users could create their own app space, and then upload files into that space. They choose an app name and an app title. Apps would be available as e.g. weblogo.terrapinlogo.com/myapp.
We may also want to register a domain like e.g. logoapps.net, and apps would be available as myapp.logoapps.net.
What would we need?
Would people be willing to pay for such a service? I am not sure. Hard-core developers like Stan are rare, and we cannot ask Stan for any money. On the other hand, if we are able to offer a free web page where people would upload their stuff, it could be an interesting marketing opportunity.
Needless to say that this service would only be available to licensed customers. Also, the number of apps could be related to the size of the license.