4 ms·
Love this approach. I tried my best to summarize what each of those apps improved on when they first appeared below: Like a teletype, but it doesn't need paper
by robenkleene 7y ago
Love this approach. I tried my best to summarize what each of those apps improved on when they first appeared below:
Like a teletype, but it doesn't need paper.
Like a line editor, but you can see all of your text at once.
Like a gopher, but with better multimedia.
For my own product, this gives me: like a web browser, but with its own local apps. Which seems pretty decent?
- dsr_ 7y agoWell, maybe. Right now we have webapps like Google Docs, where you get a clean copy of the update application, the data is handled on someone else's computer, and you can copy it locally or load it from local storage. Is this better than that?
- robenkleene 7y agoI'm not sure, to be honest. Google Docs local technology feels more like something made to supplement their online web apps. What I'm making is for more for local apps that don't have an online component. I guess that's the distinction, and it seems that a different set of uses cases emerge from that focus. To give an example, would you use the Chrome app technology Google Docs uses to install a web-base Git client? That particular example gets covered by Electron, which I also have overlap with. But Electron feels heavy for a lot of uses cases. This is why I always come back to text editors, web browsers, and terminals, these are all apps where people make a host of small customizations to fit their needs, I want an app like that that's based on a web rendering engine (and that isn't already a text editor or a terminal like VS Code or Hyper). I.e., what I'm making is more something you'd rig up to solve your problems by installing some plugins and customizations rather than a full-blown app development platform like Electron or Chrome apps.