80% of apps are uninstalled in the first 10min (especially if they ask for information or creating an account). Once uninstalled very unlikely they will ever install again. In my dev shop, I always advise clients to look into website MVP over apps unless IT IS CRITICAL to the functionality. Websites can always bring back ppl who were initially uninterested. Faster development/instant updates. Better tracking and UX a…
Start with a Website, Not a Mobile App
351–360 of 587 posts
Re: Start with a Website, Not a Mobile App
#352Earlier quoted context omitted.
I figure most things don't need an app unless they are trying to take more data anyway. Anything telling me to install an app whose mobile experience is fine already is very fishy to me. I'm looking at you, Reddit.
> Anything telling me to install an app whose mobile experience is fine already is very fishy to me. I'm looking at you, Reddit. So much this. To add insult to injury, reddit intentionally degrades the site's experience in mobile devices with tons of dark patterns pushing users to their shady mobile app.
Re: Start with a Website, Not a Mobile App
#353Earlier quoted context omitted.
> How is it difficult to get someone to install something for a test run when like 90% of app installs are test runs? As I said in my previous post I'm clearly missing something here. Why are those mutually exclusive at all? You're saying that most installations are test runs. That implies people are leery about leaving an app they don't want installed. Why does that mean that it's somehow easy to get users to instal…
>As I said in my previous post I'm clearly missing something here. Why are those mutually exclusive at all? If it was hard to get people to test drive your app, then 90% of app installs would not be test runs. They would be one time permanent installs. >It sounds like they don't want a bunch of apps installed. It also sounds like people are constantly trying new apps, no? Precisely what OP said people do not like to…
That doesn't logically follow.
Consider the possibility: Only 1 in 1000 of people who learn about your app is persuaded to install it. And then, of the small number who install it, 90% of those uninstall after 10 minutes.
I've exaggerated the numbers to make the point.
The point is it can be hard to get people to test drive your app and also have most installs be test runs.
They are not mutually exclusive.
Re: Start with a Website, Not a Mobile App
#354Earlier quoted context omitted.
>For one, you have a chance of actually finding quality native apps. Really? I can't recall ever finding a useful app through the app store. It's so littered with junk apps and deceptive copycats that discovery is a miserable experience.
Seriously?! Check out Things 3, Overcast, or Timepage (and Actions) by Moleskine. You don’t recall EVER finding a useful app?
The comment that sparked this whole thread was "The major advantage of the App Store (primarily for consumer apps though) is the fact that there's some kind of filtering at place". I don't think that's true - I think that the app stores are so littered with junk and offer so little curation that finding something on an app store is a fool's errand.
From a developer's perspective, I don't think that a native app offers any advantages in terms of discoverability or onboarding. The app stores are full of polished, well-designed apps with incredibly low download counts. A native app might be stickier than a web app, it might offer a better user experience in some cases, but installation presents a natural obstacle to previewing and sharing. I think that developing for the web should be the default choice unless you have a compelling justification for going native.
Re: Start with a Website, Not a Mobile App
#355Earlier quoted context omitted.
> (paraphrasing) No PWA competes with a native experience even development wise I'm personally too spoiled by the React debugging experience, and I'm saying this as a developer who mainly does C#. On the other hand, I know many developers who can't stand a line of JavaScript. The answer is here a huge "it depends, really".
React Native gives you the best of both
Re: Start with a Website, Not a Mobile App
#356Earlier quoted context omitted.
That's more reasonable. I wonder if these work via Firefox? Maybe that's why I've never seen them.
I normally use firefox too, maybe I accidentally opened the link in chrome last night. I don't have my phone around to test. I just remember thinking "ahh that's kind of neat" before clicking no.
Re: Start with a Website, Not a Mobile App
#357I don't even bother installing apps anymore, I don't have time to research whether or not they are going to abuse my privacy or have some horrendous TOS. I got my core 10 apps and haven't bought a new one in a year.
Re: Start with a Website, Not a Mobile App
#358Earlier quoted context omitted.
Either I'm already certain or it's necessity/desperation. If I'm actively looking for an certain type of application I will usually dedicate half a day to sign up for bunch of different apps all at once. It's pretty time consuming and I'm usually left disappointed. I will then spend the next half a day trying to remove myself from them all.
Then 6 months later one of those app companies send you an email update, by which point you've forgotten what they do, and yet they give you no hint of what the app is in said email.
Re: Start with a Website, Not a Mobile App
#359Earlier quoted context omitted.
I disagree with the 99% estimate, I too take the same approach, and recommend the same to those who will listen. I would venture that number to be at least 80%
So you are saying that out of the 3B smart phone users in the world 600M will never install a app ever because they fear the abuse of their privacy or some horrendous TOS? Yeah, no! I think your intuitive judgement failed you here