_lex

19 ms·

181.
by _lex 14y ago
I agree - I often just give up and read the source to figure out how to use advanced features.
182.
Cirque Du Soleil, in your browser(movikantirevo.com)
2 points by _lex 14y ago|0 comments
183.
by _lex 14y ago
It sounds like what you want is really good, searchable documentation for everything. I use dochub.io - it's pretty awesome.
184.
by _lex 14y ago
I like the idea, but it's really hard to read anything. There's just too much.
185.
by _lex 14y ago
I got it, and I was thoroughly impressed.
186.
by _lex 14y ago
I wonder how this is going to affect Ouya, who just raised over 8M on kickstarter, and who was relying on Onlive to provide access to AAA titles from day 1.
187.
by _lex 14y ago
People aren't building apps for fun. They're trying to build a business. No one in their right mind is going to invest in a business that's built in an area that can be bulldozed at any moment, and that's what twitter's platform is. For dev
188.
by _lex 14y ago
Twitter is making it very unappealing to build on their platform, since developers have to effectively give up a large chunk of autonomy and trust that Twitter's business model won't change again, and that Twitter won't suddenly start compe
189.
by _lex 14y ago
It looks like Twitter won't be happy until the only Twitter developers are the ones that work at Twitter.
190.
by _lex 14y ago
Hybrid apps serve the website locally, from the device, because if you didn't there would be a lot more data being sent over the wire, and your app would perform significantly worse. The only thing (well designed) hybrid apps generally use
191.
by _lex 14y ago
I think most companies that are building hybrid apps have developed a similar internal system. Good work.
192.
by _lex 14y ago
More constructive criticism: your benefits seem to really be features. To convert your features to benefits, you need to talk about likely possible use cases. For example, one "benefit" that you list is "Custom notifications", but that does