1. 2
  1.  

  2. 3

    If I’m on my phone, I want to use a native mobile app, everytime. I don’t mind too much if it contains a web frame for some of the content. But I’ll be damned if I wait 5-10 seconds for the main page/screen to load - in that case I’ll just uninstall it. On the other hand, its a thing of beauty when I can browse the content even offline. (Thanks twitter!)

    1. 2

      Do you mean a webpage that looks like a mobile app or an actual native mobile app? Also, would you suggest making a specific layout for mobile or would you suggest making judicious use of display: none; to remove unimportant elements and decrease page load time?

      1. 2

        I mean I want to use an actual native mobile app. Its ok if that app uses webview for somethings - but the main content should load fast through an API, and cache locally so I can browse instantly, even offline.

        Mobile enabled websites are ok if nothing else is available, but given the choice, I’ll take a native app. The numbers suggest other people feel the same way.

        1. 1

          Ah, ok, understood. Do you feel this way about all sites, or just certain types of sites like news sites, online stores, and social networks?

          1. 2

            I definitely do browse regular websites, but mostly on my desktop. If I’m going to visit your site from my phone, I want an app. Maybe what I want is a good RSS reader for my phone? I’ve never found one that I liked, but its been a while since I looked.

            1. 2

              If a website is designed “well” for mobile, i.e. it caches data for offline use, loads things only when needed, do you still want an app anyway?

              I realize that, like you, many prefer native apps. But, I wonder whether this is just a reaction from past evidence based on the fact that most websites are not designed to be mobile friendly, even though it is typically technically feasible to do so.

              One sad thing for the mobile web is that many seem to feel much better about websites when they are able to pin them to the home screen (like with a native app), but unfortunately the UX flow to do so usually has many more hoops than you see for installing an app.

              1. 2

                Yup, HTML5 lets you build webstuff with local cache, so that’s an a option. Definitely part of my dislike of mobile web is the UX flow to pin an website sucks. But also, I hate writing apps in javascript, and Its harder (for me anyway) to make a really tight responsive app in html vs objc/java

              2. 2

                I’m the opposite - especially for a site I just want to use once or twice or try out first. If the coffee-shop across the road has either a mobile app or a website where I can pre-order my coffee, I’m going to give the site a go, I’m not likely to search the app store and go through that process. I only want to add the app once I’m already addicted and know I’ll use it regularly. “Close Tab” is easier than “Uninstall”, and I feel the install process is easier also.