You're wrong. CalyxOS >

The shitty ram thing is especially egregious and was not the industry standard at the time, especially for your flagship phone.

The weird audio issues on multiple devices is also out of the norm.

Current pixel phones are pretty good! But it's clear that for at least the first 4 gens they had some QC and quality of parts issues.

Edit: also to add, it's a basic thing that if your phone is dead dead then you should use wall power to power the circuit to charge the battery. But if you let it sit for a few months, your older pixels will not charge again unless you put in a new battery with some charge, that is definitely out of the norm and is also something that should have been rectified sooner.

As much as like to shit on Apple for many other reasons, they've had fairly few mishaps with their phones. Even counting bending phones, "you're holding it wrong" etc., their track record is still decent compared to the competition.

I can't speak from experience outside my own issues with my 5a but supposedly they're better about that stuff now. One reason I'm interested in the 8 is the unlocked bootloader and their smallish form factor. I have a Zenfone 9 RN and I went to put lineageOS only to find out they locked the bootloader down six months after release 😭

Pixel 1 recall and class action in 2019: https://www.theverge.com/2019/5/14/18623077/google-pixel-faulty-mic-issues-lawsuit-payout-hairline-fracture

Ram issue mentioned in user forum with listed official response from google: https://support.google.com/pixelphone/thread/113517096/pixel-3-xl-bricked-overnight-computer-recognizes-as-qusb-bulk-cid-likely-caused-by-security-update?hl=en

Some of these others are harder to pin down because there's no official response but I'll do my best

Here's some users experience charging issues: https://www.reddit.com/r/GooglePixel/comments/15lj11a/connected_not_charging_how_to_fix_this/

Pixel 8 lemon unit post: https://www.reddit.com/r/GooglePixel/comments/17sa4z9/got_a_lemon_should_i_try_again_or_go_different/

Pixel 4 lemon post: https://www.reddit.com/r/GooglePixel/comments/efhcvf/my_4_week_old_pixel_4_xl_died_yesterday/

Pixel 6 buzzing issue; https://support.google.com/pixelphone/thread/148605754/loud-buzzing-noise-from-speaker-during-call-on-my-pixel-6-pro?hl=en

Pixel 3 buzzing: https://www.reddit.com/r/GooglePixel/comments/9weskv/pixel_3_fix_for_buzzing_sound_from_speakers/

Pixel 2 buzzing: https://www.androidauthority.com/google-pixel-2-xl-buzzing-rattling-speakers-825307/

Article on tensor chips overheating: https://techissuestoday.com/google-pixel-phone-overheating/#:~:text=Tensor%20brings%20the%20heat%2C%20literally!&text=While%20all%20the%20AI%20advancements,some%20reason%20or%20the%20other.

Pixel 8 screen issues customer has bad expires with Google support: https://www.reddit.com/r/GooglePixel/comments/1c3gcnz/pixel_8_green_screen_and_recall_terrible_customer/ (thought they were doing better these days, guess not)

Pixel 8 screen issues warranty extension: https://www.zdnet.com/article/google-extends-warranty-for-pixel-8-display-issues-how-to-check-if-your-handset-is-covered/ (thought this was a recall, guess not)

I've already mentioned it here, but OneUI kept the small buttons.

So apple has slowly added some of these swipe features and a lot of iPhone users were basically trained how to use them over time.

I'd honestly say swipe is a bit of a misnomer for them, it's more like eases. There's a specific way you to swipe for different things, it's nuanced. When I switched to iPhone for a year, I had to ask my gf a few questions to get the hang of it, but once you do it's super intuitive. On almost every app a swipe from the left is back and a swipe from the right is forward. And there was a different in finger action for a back swipe and a side menu. Once you get the hang of it it genuinely feels like second nature, I almost never missed my android buttons. When I switched back I tried androids swipe features and was immediately disappointed. Android's backswipe is really oversensitive, meaning that it's way too easy to swipe back when I'm not trying to. Also they're multitasking up swipe is less sensitive meaning it's harder to get to multitasking than on iphone. And of course the final nail in the coffin there is no forward swipe from the right, a swipe from the right is also just back on Android which was a real mind fuck. Currently I just use the Android old buttons, or I use the Android gestures where you have a home and back button and then you swipe for multitasking stuff. I can say that the multitasking swipe stuff seems to be better than the last time I tried it.

I would say the biggest difference is when you swipe on the iPhone it's like turning a page, a smoothe slide. Where as android it's just a flick. So when I accidentally swipe the screen, I'm going back on Android, but on iPhone I have to definitely be doing an intentional slide, and for me that slide was just short enough to not be annoying.

As a mobile developer, tiny unhittable buttons drive me batshit. I used to get handed app design documents all the time that had these little buttons, along with image files for these buttons that were just large enough (width and height) for them. I would always do a trivial amount of extra work to make the actual tappable regions larger than the images to improve their usability, but when I mentioned this to the designers they would go apeshit and demand that I restore the original tiny tappable regions, usually with the bullshit rationale of that being what end-users expected and they didn't want to verify that what I'd done to my best judgement was OK. Management would go along with the designers, on the grounds that enlarging the tappable regions required more time and effort - even though I'd already done it and undoing it would require even more time and effort.

It eventually occurred to me to just do it without telling anyone and I had no further problems.

A fun little fact about iOS: the operating system includes a private method (which is something developers supposedly can't use without getting their app rejected) named _warpPoint. This hack was put in when they started supporting landscape, because the top toolbar and its tiny buttons became even tinier and virtually unusable in that mode. _warpPoint intercepts touches near the toolbar and changes the coordinates to the middle of the nearest button - basically doing the same thing I was doing by enlarging the tappable regions, just doing it at the global level. The irony is that they still don't really work very well, despite the very existence of this method proving that Apple knows it's a general problem.

I've decided that I'll never get a phone with a boot loader than you can't unlock as long as I can help it, so Samsung is out for me