From a developer perspective many of these inconsistencies are rooting from inconsistent access patterns - operating system (ABI?), applications (ICP?), remote (TCP, HTTP, LDAP, FTP, ...?). All of these are "execution" or "information" but have to be programmed against differently.
s/ignorance/apathy
Those aren’t options, they’re fantasies. Like dreaming of suing out of existence a company that wronged you, or fixing the world by ruling it, or winning the lottery without playing.
Android isn’t perfect either, it’s a different set of frustrations. And why would Apple ever need to hire you for that specific task, do you really believe there aren’t engineers inside just as frustrated as we are?
The way I see it, the yearly release cycle is to blame. No one inside the company has time to do anything properly anymore. Features are announced and rushed every year, and we’re reaching the point where by the time something which was announced at a WWDC is out of beta, we’re preparing for the next one.
What these companies need to do is slow down and stop chasing every shiny thing. You know, like Apple used to do with macOS. Tim Cook needs to go.
I'm not saying nobody can be like Steve Jobs, but Steve Jobs was an anomaly when it comes to C-Levels, and even when it comes to management in general, at least from reading things like www.folkore.org and interviews with people who worked with him.
And I'm not even talking about talent or vision or whatever, it's just about saying no to pointless features that are there for someone's ego or so that someone can get a promotion.
https://mjtsai.com/blog/2025/02/26/testimony-on-external-pur...
I’m not saying anyone will be better than Tim Cook, I’m saying he’s actively bad. Will his successor be actively bad too? Maybe, but the sooner we find out, the better.
The general publics opinion of Apple is that they are golden and untouchable, the best tech company out there. The reality is much different.
So why isn't that happening?
- Because a lot of journalists are Apple fanbois
- The press publishers don't want to sour relationships with Apple (because of advertising deals)
- Publishing bad things about Apple would infuriate the many Apple fanbois among the readers, causing a shitstorm against the medium
There is even a joke amongst Apple developers who all know that Apple’s claim of “don’t go to the press, it never helps” is a blatant lie as it’s the one thing that works.
Not "never", but it is indeed my observation that the press is much "nicer" in their reporting and much more "forgiving" to Apple than to other similar companies.
In some circles, this observation already has become a running gag when the pen pusher is again too impressed of some Apple marketing.
The advertising deals with apple are not that lucrative, iirc.
So bad reviews are avoided to ensure the media gets the early review clicks.
Yes, you may implement a solution more efficiently by not overengineering it. But at some point constant seek to reduce "complexity" so that more features fit into sprint (funny how story point measure complexity, not time, but sprint is sized in both time and SP capacity) is bound to hit feature completeness. Once you cross over that metaphorical Rubicon it's game over - quality starts to slowly go downhill.
You will not notice it immediately. That edge case that was ignored may not surface for months or years. It may take several idiosyncrasies to line up for a feature to be declared FUBAR. At some point that technical debt does bite you back, but at that point the process (tm) has already optimized away most if not all opportunities for deep refactorings fixing previous rushes to deliver.
Furthermore, Sprint Planning/Refinement are just innocuous ceremonies whose only aim is to facilitate productive discussion between a Product Owner/Manager and an Implementation team as regards delivery timelines and priority ordering thereof. Done properly, it allows a pragmatic approach to achieving a predictable software delivery cadence via mutual compromise.
If the process turns into 'fit as many features into the sprint as possible' at the expense of Performance/Stability/Functionality or Technical Debt accumulation, you're really just doing the 'fast' version of Cheap/Fast/Good Waterfall Project Management.
I never buy products when they are first released. I prefer to wait at least 3-4 months so that production has had time to tweak all the settings and weed out the funky first component deliveries. Also the software devs will have fixed the worst bugs by then.
Who is dealing in fantasies now, friend? :)
Apple's software really isn't in crisis. It's just very low quality relative to what people who've written software for a living know to be possible.
But it doesn't matter - Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.
It's not that they're chasing shiny things. They're cosplaying competence and they genuinely don't know it. They think they're actually competent, elite really, because they attend 'elite' schools, get good grades and go work at the 'best' places.
They have it ingrained in them that anything a poor person says can be disregarded because poor people are losers, because they're poor. They're an unintentional suicide cult. They genuinely don't know it. You can't convince them of anything because they are rich. If you complain - go see a therapist, there's something wrong with you.
You can youtube search Garys Economics. It's a poor kid who slipped into the rich kids club and defected. It's quite eye opening.
I said they need to, not that I think they will. But they have in the past. There is a reason Snow Leopard is still lauded today.
> It's just very low quality relative to what people who've written software for a living know to be possible.
No, it’s low quality relative to what Apple users came to expect. There was a time when “it just works” was an aspirational goal which permeated their decisions and you could see the results.
> Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.
What a bizarre conspiracy theory. No company gets to that stratospheric level of success by making hiring incompetent rich kids their primary goal.
By the way, I did catch the rant you posted before. I tried to reply to it but after writing it up and hitting reply, you had already deleted it.
You've gone ahead and made it the first goal in the context of all goals a company has (thus making it 'primary').
That's not a legal move :)
Re-reading my own post - the bit you narrowed in on is the least interesting and controversial in my mind.
We know rich parents do all sorts of things to pad their kids' resumes to get into fancy schools. We know kids game the system to get highest possible grades. We know kids grind leetcode to get the job. We know companies prioritize hiring according to school, grades, ability to pass leetcode. We know people very often prioritize their career trajectory above needs of the company. We know companies prioritize stock price over delivering value to consumers.
I just shortened into a single sentence and you've misunderstood it to mean something bizarre. Oh well.
I don't see a connection between yearly release cycles and a broken notes application. They shouldn't be doing anything that is particularly affected by such changes and the problem they are trying to solve has been mostly solved for 40+ years now.
While it certainly applies to some things, there's a different, bigger issue happening as well.
My understanding is that Apple outsources loads of software not seen as "critical". I think that's the first place for them to look.
Some of this could be resolved by open sourcing their less important apps like Files, Notes or Home which barely ever get touched, yet are full of quirks and bugs. Those apps should be public examples of good SwiftUI coding.
At many places where I've worked, the mentality is: "If that bug didn't block last year's release, then why would it block this year's release?" So it survives one release, it never gets fixed.
1. If you copy some text
2. Select other text
3. Paste the text you copied to replace the selected text
Notes will crash. This has been known for years.
Also if you turn off all suggestions in Spotlight on iOS and just use it as an app launcher, it will still take seconds for Spotlight to show you the results. For something that's supposed to be an indexed look up.
I don’t mean to be rude, but that’s how an iOS intern would implement it.
A bad one maybe
Not sure about iOS, but Android has sort of magnifier when users start to select so they can clearly see what characters they are selecting. It definitely helps. However, what I should want is some sort of arrow keys that I can press to select characters instead of relying on my fingers.
I wish they implemented backspace like they do with fine scrubbing on seekbars. i.e. you could move your finger up & down while holding the backspace key to select the granularity of deletion between letters, words and paragraphs.
No, Ellie isn't a typo and I didn't actually mean Emma.
Cannot get notifications for new mail on iOS.
On Languages:
Cannot swipe-to-type and dictate in less spoken languages even though this has been possible on Android for over a decade.
That's extremely serious because the call you're trying to make could be an emergency call. A bug like that would have top priority in the org I used to work in. If I'd had to guess it cancels the call because there's a crash in a process somewhere. Possibly because of audio handover between apps.
Can't think of any more at the top of my head ... it feels a lot like Windows, where there are a bunch of eternal bugs one just sort of knows and works around, even though it's a kind of shitty and occasionally very frustrating experience.
Reminders too. For at least 5 years, creating multiple reminders in a certain order will not create multiple reminders, and will just append the text to the end of the first one. Surprise — hope you didn’t set any important reminders in that batch!
And the great thing about their standardization between iOS and macOS code means the exact same bugs exist in both versions. Yay.
Sometimes 3s will pass before I even see anything after I've already typed in my search term (I'm always searching for a local app btw - it's how I open apps).
It's like it waits on an http request for every keystroke.
Also, you used to be able to search for an app in any of the secondary languages you have in your settings. Which is great because apps have different names in different languages (Settings vs Configuración vs Réglages), so it would be annoying to have to remember which word to search based on which language is primary. For years it would show you multilingual results (e.g. you can search for "Settings" as long as English is one of your secondary iPhone languages yet "Configuración" or "Réglages" would still show up).
It was the sort of polish I came to expect from Apple. Well, that stopped working a couple years ago.
I’ve only ever noticed maybe like a few actually bothersome bugs in the however many years I’ve been using iPhones which is pretty impressive.
Anyway, hope they get it together. Performance and optimization are a very difficult and very thankless job that might not get you promoted the same way cool sexy feature work does. Such is corporate life I guess.
I face none of the issues on my Samsung S23 phone, which the parent commentator describes - no issues in phones calls (I make 4-5 calls daily, mix of WhatsApp & regular calls), no major issues in Google Keep (which I use 2-3 times daily, specially never of a note becoming "blank"), and again no major issues in the Google App Store or updates (which I use on an average once a week).
So maybe, the software quality varies by user experience rather than one platform being universally better.
As for all Apple software, I might use Preview or Numbers (spreadsheets) on occasion, and I'm forced to use Finder, which I hate. And Terminal works well. I avoid Safari.
Apple "PC" hardware is solid. I use third party apps though, little Apple software, there are better alternatives. I've used Android since the HTC Dream (I think it was the first Android phone in the USA) and have stuck with Android since, with few problems.
Edit: I thought the Apple Vision Pro would be interesting (I couldn't justify the expense) but I saw the value supposedly would be greatest for those fully bought into the integrated Apple app ecosystem and iCloud. I'm not the target user.
Same. I have two "deal-brakers" when it comes to notebooks: 1) it's got to sleep consistently and without problems when I close the lid. 2) it should be silent when I'm doing simple things or nothing at all.
I have never seen a Linux or Windows laptop that does these things well. Even Intel MacBooks would spin up the fans seemingly at random. I don't think I've ever heard the fan in my M1 MBP. I'm looking forward to the new M4 MBA to replace an older Windows 10 laptop, which spins up its fans all the time, and sometimes doesn't sleep, sucking the battery dry in the process.
Had to swap the WiFi module to get the power management to work properly.
AND I can use Linux, which is a dealbreaker for me as my favorite operating system.
Yes, arm and riscv are interesting. I will definitely test them in the next ten years if they still get better. For now, x86 is still the best platform for me.
It goes back to 2019 - certainly more than 100 calls
I'm triggered. How many times have you reached for the 'end call' button, but the other person ended the call a moment earlier than you, and as you press down the screen immediately flips to your "recent calls" screen and you call a random person straight away?
This is such a common and terrifying experience for me, and yet it's been the default UX on the Phone app since probably day 1.
and this is such an easy fix, just don't make components touchable for X milliseconds after they are visible, some value below average human reaction time.
this could of course get in the way of people quickly navigating via muscle memory, but there's a probably a threshold where it can prevent one without affecting the other.
https://medium.com/p/31773fe6bbd5
I consider it by far the most annoying bug in touch UI's today.
Solution: There must be a small interaction-ignoring delay instituted when any control has just moved to its final rendered location.
In Calendar (macOS) create a new event.
In the start or end time, type in the Minutes field, but type slowly.
For example, type "2" pause a bit, then type "1"
If there's more than ~300msec pause between the two keypresses, the 2 changes into "02" and then the 1 overrides it, so you end up with "01" instead of 21.
Works with any two kepresses. Same problem in the date fields.
Completely wrong, and super bad for accessibility.
Take basic functionality - a phone app (calling). After certain audio sessions use (calling via WhatsApp) I can’t make regular calls over cellular - the UI app immediately cancels the call. Only reboot helps.
Or notes - for many years/iOS versions, they lived with a bug where a text note may just become blank - and only restarting Notes app makes it visible again.
Or AppStore - if an app has to be updated (I have auto updates off) - and I press Update - it gets downloaded, installed - and then AppStore is back to showing “Update” button! If you just go to the app, it’s a new version. But if you press that “Update”, it will redo update from scratch.
Sometimes I’m so frustrated, and thinking of my options - it’s either move to Android, or go get hired at Apple with a mandate to fix bugs in various products… but knowing Apple secrecy culture/silos, it’s not going to work, and requires change in their hiring process/perf review/QA.