News for hackers. Stuff that matters.

A comment on Start with a Website, Not a Mobile App. Parent comment

Re:Start with a Website, Not a Mobile App by noobiemcfoob on Friday January 04, 2019 @11:38AM (#18825311)
Too many applications abuse notifications and background processing anyway. If you need those features, you have to convince of far more value before I'll install a thing.
[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by billmalarky on Friday January 04, 2019 @12:04PM (#18825595)
I'd wager you are not a great representation of the market that 99% of apps serve. Apps abuse those features because it works well for their business.
[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by M2Ys4U on Friday January 04, 2019 @12:38PM (#18825907)
>Apps abuse those features because it works well for their business.

In the short-run anyway...

[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by reaperducer on Friday January 04, 2019 @01:53PM (#18826597)
This is true.

I allow certain apps to use notifications because there are things that I want to be notified about. My card balance from the Starbucks app, or breaking news from the New York Times app.

Both of those companies started abusing notifications. Their apps are no longer on my phones.

[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by noobiemcfoob on Friday January 04, 2019 @01:32PM (#18826443)
> I'd wager you are not a great representation of the market that 99% of apps serve

I'd wager no one is. Snapchat has 200 million users. There's some 4 billion people on the internet. Niches are niches, and no one serves everyone.

[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by mktguru on Saturday January 05, 2019 @05:40PM (#18834742)
I wish "no one" was my customer then I could get a $40B IPO serving everyone :)
[ Parent | on HN ]
Re:Start with a Website, Not a Mobile App by scarface74 on Friday January 04, 2019 @11:41AM (#18825347)
If you want an iOS app not to “abuse” background processing, there is a setting that will disable the ability on an app by app basis. Of course you have granular control over notifications and how they are presented on a per app basis.
[ Parent | on HN ]