Live data from Hacker News

Prisoners of Google Android development

solutional.ee

191–200 of 318 posts

Re: Prisoners of Google Android development

#191
post #73

Earlier quoted context omitted.

> I'd prefer to get rid of the app and just have users go to the website and install the PWA, but the average user still doesn't know how to do this I think you misunderstood users, it's not just ignorance. I want apps to go back in the direction of real(not cordova) apps, not some low effort web thing. Basically zero web apps match the experience of a well crafted actual app.

I agree with you in many cases. At my professional company, we've made the decision to write native apps for Android, iOS, Windows, and the web, because we have pretty deep integration into each platform and want the best native experience for our users. But, for my personal apps (which is what I am talking about in this thread), I can't support that. Writing it once and maintaining it takes up enough of my free time…

> This app also doesn't have any integration with the system

And this is suppose to be an argument for web apps?

Re: Prisoners of Google Android development

#193
post #182
post #164

Earlier quoted context omitted.

That's not what I said, I live half my life within browsers. But big chunk of the population that you are probably not thinking about is not like that. My mother in law is using browser to read on her computer, and will never do that on her phone - the screen is too small and the whole experience not something that fits someone at her age. On the other hand, my children use apps since they are two years old, and at t…

The screen is too small to use a web browser, but not too small to use an app? Can you explain what you mean? This doesn't seem at all reasonable.

The screen isn't too small to use web browser presenting site that looks just like the app, obviously. It is too small for comfortably reading or using the browser in general, so using the phone's browser for searching stuff on google is something that many older people simply don't do (in my anecdotal experience, I have no hard data to back this claim up). Searching for the train times in city z, going into a web site and finding that it is actually identical to the app and just as useful is something that is very unlikely to happen to my mother-in-law.

Re: Prisoners of Google Android development

#194

Earlier quoted context omitted.

In my case, I was hired to work on an update to a legacy app ~8 months ago. So this is my first round of bs. Been writing software for 20 years and I’ve never seen this before… I wouldn’t consider it playing dumb, I’ve just never had cause to care or receive an email like this.

You’ve been writing software for 20 years and never had to update an app for a new operating system version?

Not with a deadline (aka Windows).

I usually work on the backend and/or front end (Web). This is a pretty new world for me.

Re: Prisoners of Google Android development

#195
post #141
post #51

I also got this email, but professionally and personally. Personally, I voluntarily built and run open source apps for 16 different cities for their transit system. This gave me two weeks to update 16 apps, for no benefit of anyone. My app is a PWA, and the Android version just uses cordova + a few plugins to add a few native options. Unfortunately, updating cordova to support the new target android api broke some of…

Your customers have been using websites for much longer than they have been using apps. I simply don't buy that they can't understand how to use a website. Stop underestimating your users.

It's a minefield. I was in Sedona, and wanted to check the real-time shuttle schedule.

DOWNLOAD THIS APP.

I'm like: I'm on this website? It's an API call. Make the API call from the friggin' website.

Edit: I'm an idiot. On the screenshot where they refer you to the application it actually shows a URL:

https://sedonashuttle.transloc.com/routes

Enjoy.

Re: Prisoners of Google Android development

#196
post #141
post #51

I also got this email, but professionally and personally. Personally, I voluntarily built and run open source apps for 16 different cities for their transit system. This gave me two weeks to update 16 apps, for no benefit of anyone. My app is a PWA, and the Android version just uses cordova + a few plugins to add a few native options. Unfortunately, updating cordova to support the new target android api broke some of…

Your customers have been using websites for much longer than they have been using apps. I simply don't buy that they can't understand how to use a website. Stop underestimating your users.

If his customers are under 25 or 25 probably not. There are also plenty of older people in the US who never had a computer. But they now have smart phones.

Re: Prisoners of Google Android development

#197
post #170
post #155

Earlier quoted context omitted.

This is exactly how Android works. But because API changes bring privacy and security improvements, scummy software used old compilation targets to abuse backwards compatibility to avoid complying with privacy and security practices. This is why Play slowly enforces apps to raise their compilation target and implement safer APIs. It's lagging for YEARS after API changes, so there's plenty of time to fix apps. The OP…

I'm the OP and wanted to clarify in case you missed some points - it is a legacy application which does not have any active dev teams on it and needs only developers attention when Google says so and as mentioned by multiple other commenters here the first time I got that e-mail from Google, was at 18th of August. I would not agree that I have been lazy, but instead trying to solve this problem in the time-constraint…

My mailbox shows Play comms warning about these changes in July, April and October 2022. And that's just a glance.

Re: Prisoners of Google Android development

#198
post #182
post #164

Earlier quoted context omitted.

That's not what I said, I live half my life within browsers. But big chunk of the population that you are probably not thinking about is not like that. My mother in law is using browser to read on her computer, and will never do that on her phone - the screen is too small and the whole experience not something that fits someone at her age. On the other hand, my children use apps since they are two years old, and at t…

The screen is too small to use a web browser, but not too small to use an app? Can you explain what you mean? This doesn't seem at all reasonable.

My 80 year old dad struggles trying to type on his phone. He uses voice to search YouTube videos for sermons, music, how to videos and to make calls.

Re: Prisoners of Google Android development

#199
post #158
post #72

Earlier quoted context omitted.

The problem is that many of my users are temporary. For example, I have an app for the public transit system for a resort town in Colorado. The town has a decent, albeit small bus system. They technically have an app from their vendor, although it is not very good and is difficult to find. If you search for "$town_name transit app", it won't show up anywhere, where as my app does. And I think my app is much more user…

> If you search for "$town_name transit app" Do people really search for entirely temporary/short-term/single-use use apps, like for a resort town's transit or a restaurant? For me it's a last resort thing, if there's no website or it's unusable.

Yes and people still watch TV even though you “haven’t owned one in 10 years”.

Or do you think places are making apps that no one uses?

Re: Prisoners of Google Android development

#200
post #146

Earlier quoted context omitted.

> it's just that most users really have separated in their minds (not surprising due to history) that apps come from app stores, and the browser is used for websites. Right, because for a very long time (and maybe still) PWAs have been much closer to terrible websites than good apps. They generally don't have the same UX properties as real apps. Remember when the iPhone first came out and web apps were the only optio…

Just looking through the apps I currently have open… Bank app, chat app, maps, Tile, YouTube and a weather app. Only one of them is actually doing anything that wouldn’t fit a PWA. So why are they apps, not a collection of links?

I would say only the weather and bank apps would be really equal as a PWA.

Maps require complex gestures and advanced graphics and UIs that would never work well as a PWA. Try maps.google.com. Its nothing like the Google Maps app. Plus Android Auto integration.

Tile probably needs pretty deep Bluetooth integration and background processing that the web doesn't provide.

YouTube can do things like PiP that you can't do on the web.

Post reply on HN