3 ms·

Very cool! What lead you down this path? This is not too far from creating a client using the web view container and letting users specify urls to their "apps"

Very cool! What lead you down this path? This is not too far from creating a client using the web view container and letting users specify urls to their "apps" with perhaps certain JS hooks or CSS classes being required of apps to be rendered/used correctly in your client. Take one step further and you could just build a browser and user apps are any valid url with no restrictions. You can see where am I going. Just wondering about what led you to your idea?

gliechtenstein 10y ago
I just commented below to another question that may answer your question https://news.ycombinator.com/item?id=11884901 https://news.ycombinator.com/item?id=11884901 I think HTML/JS/CSS have become too powerful which is a good thing, at least on desktops. But when we bring that power onto more specialized devices such as our smartphones it works as weakness instead of strength. For example, people may love super rich interactive websites on desktop but it becomes pretty much useless on our phones, which have small screen. But browsers still need to ship with these features because that's what they're supposed to do--follow the web standards. I am actually working on a blog post to talk about this in more detail, probably will publish in next couple of days. Please follow me on www.twitter.com/gliechtenstein if you are interested. As for how this was conceived, I've been working on quite a few apps last couple of years, some I released some I didn't. One of the apps I'm working on is http://www.textethan.com http://www.textethan.com and I got frustrated how I have to rebuild everything whenever I had something to change, so I built everything into a markup. Then when I looked at the end result I saw something that can be potentially very powerful so I decided to extract it out into its own app. Hope this answers the question :)
- jayd16 10y ago
  I understand your complaint but I disagree with your solution. As much as I hate working in html and js I don't think fragmenting the web like is the right solution. My ideals are much more aligned with something like Google's Accelerate Mobile Pages. I'd be a lot more interested in a project that uses AMP html to build a native app over a custom json spec.

gliechtenstein 10y ago

I just commented below to another question that may answer your question https://news.ycombinator.com/item?id=11884901 https://news.ycombinator.com/item?id=11884901 I think HTML/JS/CSS have become too powerful which is a good thing, at least on desktops. But when we bring that power onto more specialized devices such as our smartphones it works as weakness instead of strength. For example, people may love super rich interactive websites on desktop but it becomes pretty much useless on our phones, which have small screen. But browsers still need to ship with these features because that's what they're supposed to do--follow the web standards. I am actually working on a blog post to talk about this in more detail, probably will publish in next couple of days. Please follow me on www.twitter.com/gliechtenstein if you are interested. As for how this was conceived, I've been working on quite a few apps last couple of years, some I released some I didn't. One of the apps I'm working on is http://www.textethan.com http://www.textethan.com and I got frustrated how I have to rebuild everything whenever I had something to change, so I built everything into a markup. Then when I looked at the end result I saw something that can be potentially very powerful so I decided to extract it out into its own app. Hope this answers the question :)

jayd16 10y ago
I understand your complaint but I disagree with your solution. As much as I hate working in html and js I don't think fragmenting the web like is the right solution. My ideals are much more aligned with something like Google's Accelerate Mobile Pages. I'd be a lot more interested in a project that uses AMP html to build a native app over a custom json spec.