4 ms·
It doesn’t run on my phone. Even if it did run on my phone, I wouldn’t run it, because Google. Now, on the one hand, this is just me being an annoying, Apple
by the_other 6y ago
It doesn’t run on my phone.
Even if it did run on my phone, I wouldn’t run it, because Google.
Now, on the one hand, this is just me being an annoying, Apple fanboy, tracking-resistant outlier. But on the other hand, “you” targeted the web BECAUSE it’s the open platform for the widest range of users. “You” decided against a native app so as to cut costs and produce a more consistent/responsive cross-platform application. “You’ve” already saved the money it would have cost you to support multiple OSs. Use some of that saving to support the web.
- joombaga 6y ago> Use some of that saving to support the web. Or don't. I don't get mad when people write bash-specific scripts that won't work on all POSIX compliant shells. This seems analogous (though admittedly non-compliance to web standards has a larger impact than non-compliance to shell standards). Perhaps Chrome removed enough barriers for the tool to exist at all.