3 ms·
Are mobile devs not eating their own cooking anymore? I can't do anything on a smartphone anymore, outside of some very well worn ruts, that doesn't involve enc
by stcredzero 11y ago
Are mobile devs not eating their own cooking anymore? I can't do anything on a smartphone anymore, outside of some very well worn ruts, that doesn't involve encountering some annoyance like this somewhere between twice an hour to every other minute.
- peterhunt 11y agoAre you using native apps or mobile web?
- exodust 11y agoSurely it's obvious what he's referring to. Even if you try living your whole smartphone life inside native apps (which would be sad), you inevitably get sent out to the web via links. Opening in your phone's browser or through the native web view. The native "web view" is often an inadequate browsing experience, and will have the same annoyances as the full browser anyway, only worse because it's a cut-down version of a browser, tethered to the native app that doesn't want you straying too far. To the point about dev's eating their own cooking. It's a fair question, but one I think increasingly is about project managers and non-developer stakeholders calling the shots on things because "everyone's an expert" in the web dev kitchen.
- deleted 11y ago[deleted]
- x0x0 11y agoOf course not. Have you tried using twitter via mobile web? Stuff is broken all the time. They clearly view the site as leadgen for their applications.