4 ms·
the author totally skips the UX concerns I don't get your point. People do UX design on the web. Instead of opening your NYCSubway app, you just type "NYCSubwa
by erikpukinskis 16y ago
the author totally skips the UX concerns
I don't get your point. People do UX design on the web. Instead of opening your NYCSubway app, you just type "NYCSubway" into Google, touch the first link, and now you're on nycsubway.com, whose UX has been meticulously crafted just like the NYCSubway app.
The point is that downloading apps is an unnecessary step.
- mrbogle 16y agoIt seems the article is talking about having some search interface call some data providers, then display the data returned by the providers. I imagine what your parent was trying to say was that the search interface cannot generify the display and interaction with the data provider's data.
- roc 16y agoPretty much. The author's identified 'problem' is: I can't find a subway map when I need it because it's too difficult to find and install 'an app for that'. My reply was working from the assumption that the author was proposing a solution that was designed to address that. If the context-sensitive search site is merely identifying that I'm looking for a subway map, and then forwarding me on to one of 10,000 disparate subway map web services as erikpukinskis seems to be suggesting, users will inevitably bookmark the web service interface they like best and query it directly in the future. Leading to the same use scenario as with apps. The only differences being trivial technical ones (from the standpoint of the user).