5 ms·
> years ago the Instagram activity feed was rendered in a webview Isn’t the instagram activity feed just a big scrolling page of images and text? It doesn’t ex
by marcellus23 5y ago
> years ago the Instagram activity feed was rendered in a webview
Isn’t the instagram activity feed just a big scrolling page of images and text? It doesn’t exactly have a lot of interactivity or animations and transitions, so maybe not the best example for what can be done with web APIs. Lots of native apps use web views for individual screens that display mostly static content, but that’s not really what’s being discussed.
- afavour 5y agoMaybe we disagree about what’s being discussed: “mobile app made with web tech” definitely falls into that category for me. I bring it up because it isn’t hypothetical for me, I’ve received pushback against using webviews in these situations because “web stuff always looks awful” and I know that to not be the case. In any case the vast majority of native apps aren’t much more that scrolling lists themselves! Sometimes I think we overcomplicate our image of what native apps usually are. The OS-provided transitions between views are one of few big differentiators, IMO.
- marcellus23 5y agoBut then that’s just a native app that uses web views for some pieces. Every app does that. Native transitions between views are exactly what the posted link is discussing. For static content, of course there’s really not a difference. It’s the interactions that matter.
- dmitriid 5y ago> maybe not the best example for what can be done with web APIs. Well, the page sucks. If they can't make such a simple thing right, perhaps wait before making something else? BTW almost all such pages on the web suck (Twitter comes to mind) and are worse than native versions