Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Oreo

android.com

Post reply on HN
Print view View original

271–280 of 658 posts

Re: Android Oreo

#271

Post by ehsankia »

TACIXAT wrote: post #223
jampa wrote: post #36

I know this is a non-issue for many, but those emojis look really dated. Every update they get harder and harder to read in small form. One of the things I observe, mainly on Instagram Stories is only people with iOS post with emojis attached, I never see Android ones. Too bad there is no way to install custom emojis in any system (without rooting/registry tweaking), like we do with fonts.

I absolutely hate those emoji. It's the gradient and outlines, it looks like bad enterprise design. The flat blobs were great.

Yep, new emojis look absolutely awful. They are so out of touch with what their customers want. It's like the emojis were made by some robot or algorithm that is trying to optimize the wrong parameters. I mean, just look at this comparison: http://i.imgur.com/apqo9Ry.png

Re: Android Oreo

#273

Post by ehsankia »

ufmace wrote: post #250
komali2 wrote: post #143

Going to take advantage of an Android thread here to ask something that has driven me crazy for ~3 years: How do I disable "pop-down" notifications? i.e. facebook messenger, on receiving a message, drops down a little message box from the top with that message. It stays there for about 2 seconds and then disappears... unless further messages in that chat appears. The only way I can disable this is by muting that chat…

Swipe a notification to the side a little bit, and you get a gear icon. Tap that, and you can set that app's max allowed notification importance. You can block all notifications, relegate them to only being visible when you pull down the notification bar, or allow normal icons but not "peeking" notifications.

Yep, there's a new feature in Android O that gives you full control over notifications. You can have them make a sound and pop up, only make a sound, make no sound, or not show up at all. And you can set that per app, and even per notification type if they are targetting O api

Re: Android Oreo

#274

Post by mjevans »

kevincox wrote: post #132
dcow wrote: post #60

Am I the only one who's really disappointed by the platform's shift in its stance on background execution? I was originally drawn to Android because it wasn't iOS. I wanted to develop on a platform where I could run a service in the background if the user wanted that. Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users and removed if they were too poor. You can be…

You can disable "Battery Optimization" per app, so this isn't very restrictive. It just applies by default.

I'd like to do that, but when I 'exit' an app and/or swipe it off of the list of program cards I want it to ACTUALLY exit (at least within 30 seconds).

Re: Android Oreo

#276

Post by dcow »

klondike_ wrote: post #100
dcow wrote: post #60

Am I the only one who's really disappointed by the platform's shift in its stance on background execution? I was originally drawn to Android because it wasn't iOS. I wanted to develop on a platform where I could run a service in the background if the user wanted that. Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users and removed if they were too poor. You can be…

That might be good for power users, but for the average user it's a disaster. How many people actually read the app permissions when they install something? Most apps request background privileges and if you don't like that your only other option (until recently) was to not install the app. Users blame Android when Facebook and other popular apps started eating all their battery by running in the background. Google's…

Yeah I understand why we're in this situation. I'm lamenting the fact that it's reached this point. Maybe I'm a minority but I don't think my apps are the hottest shit around and I try to make an effort to be a good steward. IMO engineers should push back when product asks for things that clobber system resources. However the few bad examples should not ruin it for the use cases where you really do need something running in the background. I also partly blame these DI solutions that encourage devs to stuff everything in a graph they do or don't realize is tied to their application instance. I've seen this multiple times in production apps.

Re: Android Oreo

#277

Post by ehsankia »

Asdfbla wrote: post #174

I know programming within the constraints of mobile devices isn't easy and I want to take nothing away from the release, but when you are still used to Desktop computing it's kind of funny to see how seemingly trivial nice to have features like picture-in-picture or notification dots get all hyped up in the press release.

Does desktop have good PIP? It obviously matters much less when you have multiple monitor, but I'd love to see OS level PIP support on desktop. Aka, have a video "always on top" in the corner that I can move around and resize while browsing the web, all on the same monitor. Some programs have "always on top" support but there's nothing OS level.

Re: Android Oreo

#278

Post by catdog »

dcow wrote: post #60

Am I the only one who's really disappointed by the platform's shift in its stance on background execution? I was originally drawn to Android because it wasn't iOS. I wanted to develop on a platform where I could run a service in the background if the user wanted that. Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users and removed if they were too poor. You can be…

At least in Android 7 you can explicitly allow this for a specific app. This question can even be triggered by the app itself (e.g. Conversations and Signal ask you to do this if they can't use GCM). This is hopefully still possible.

> It's the turning of an era for Android, and my interests have moved elsewhere (from an app platform perspective, embedded Android is still vialble since everything you ship runs as a system app with no restrictions).

Google making it more and more difficult to avoid gapps is nothing new.

Re: Android Oreo

#279

Post by ehsankia »

lotyrin wrote: post #50
fenwick67 wrote: post #22

"new emoji" is an OS-level feature now. Welcome to 2017.

Well, there was a lot of distaste for the previous style, it's a pretty notable difference to users. (For the record, I liked the original "blobs" and will miss them.)

I'm fairly sure anyone who has actually had a proper look at the new emojis much prefers the old ones. And I'm not talking just about the blobs (which were only a small fraction of the emojis), but rather the overall style with the gradient and border, and the drawing for the animal emojis too.

Re: Android Oreo

#280

Post by xorcist »

Karunamon wrote: post #23
maxsilver wrote: post #18

Earlier quoted context omitted.

Or even if just gets the chip manufacturers out of the equation, that alone fixes most of the problems. The OEM side is usually pretty easy / trivial in comparison. And there are a number of OEMs who would happily push updates but can't, because they can't get hardware packages from Qualcomm / Amlogic / Freescale / etc. That, more than anything else, holds back new Android releases on lots of hardware.

Supposedly the carriers are real pains as well. I've heard horror stories of months-long approvals processes on Verizon and AT&T ROMs. It's a game I wish they'd get out of entirely. There's no such thing as a useful carrier overlay.

Carriers are a red herring. The world at large couldn't care less about how the customers of AT&T can supposedly only install AT&T-approved firmware. Most people can, but they're not seeing any updates.

Google needs to fix their upgrade story. Even if the North American customers continued to run old vulnerable versions forever, updating everyone else's systems would be a tremendous improvement. (It would also make it difficult for the US carriers to continue those particular business shenanigans.)

Post reply on HN