I've been using all Apple products for almost 10 years, still do, but I've almost lost faith in Apple's ability to engineer reliable software. It's gotten really bad lately.
It's sad, because I really like their whole infrastructure with iCloud and sync between devices.
I don't know what happened, maybe they just have too many products and operating systems to support.
If you ever look under the covers at how Apple products are programmed you will know why. I'm not a big fan of Microsoft but if you compare, for example, the programming documentation on MSDN to Apple, it's night and day. Microsoft has clearly documented 95% of their APIs and for the most part, they are stable. Apple's APIs change constantly and are poorly documented. The documentation they do have is incomplete and full of dead links. How can you write good software on top of this?
I agree that Microsoft's documentation is stellar for their Windows APIs. Apple's is noticeably worse.
However Microsoft's APIs are not "more stable" than Apple's - in fact the Microsoft APIs change constantly. See Win32 -> MFC -> WinForms -> Silverlight -> WPF -> UWP -> WinRT... Or for languages, maybe you want to use or C++/CLI or C++/WinRT or C# or VB.NET or F# or JavaScript or the language they'll introduce next week. The treadmill is real and exhausting; what is a modern Windows app anyways?
For comparison Apple wants you to write Mac or iOS apps in Swift, or in Objective-C if you can't use Swift.
> However Microsoft's APIs are not "more stable" than Apple's
You can pretty much always run apps for Windows XP (released 2001) on Windows 10. You can't run any apps from OS X 10.0 (released the same year) on modern macOS. Yes, there was a processor architechture change in there (and a subsequently dropped compatibility layer), but the APIs have changed enough that that isnt the main issue.
Microsoft abandon the entire API, and replace it with something new every couple of years (the grandparent comment has a good list). This has the benefit that once software does work it should continue working more or less indefinitely.
Apple have mutated the same API over many years, however Xcode's default settings drift, deprecations are frequent, and the new macOS is rarely backward compatible with a large application. This means that each summer when the new Xcode/macOS combination is released you have to spend some time getting up and running again.
I doubt that the ideal situation of a continually developed API with perfect backwards compatibility exists. In that case the getting your code building and running with the new Xcode/macOS each summer is likely less time consuming than rewriting against a new API every 5/10 years. If you are maintaining well established code, then the opposite is true.
I recently installed something that was probably first targeted Windows 98.
The APIs listed by GP are deprecated and the platforms are not shipped/enabled by default, but that's worlds apart from intentionally breaking them (with almost no communication).
Of course, I still prefer a good package manager and direct access to the source on GitHub/GitSomewhere, but MSDN is very well maintained.
Microsoft is a little weird. The safe bet for a desktop application is to do it in WinForms. I'm pretty convinced that Winforms will outlive any of the newer frameworks from Microsoft.
The XAML developers will jump to whatever the next thing is when it comes around, but the conservative WinForm developers won't go anywhere anytime soon, forcing Microsoft to continue supporting and developing Winforms.
Throwing together a quick WinForm application is still much faster than building something using XAML, in my opinion. Especially if you don't know what you're doing, and that still how many in-house business applications seem to be built.
MS has backwards compatibility for existing software, but it's a gamble to start a new project using MS tech, you don't know what they will cancel, rename or invent next year.
Apple doesn't have backwards compatibility for existing software and stuff breaks regularly from version to version. However, one can count on Objective-C to pretty much work (although Swift is still work in progress).
I generally like MSDN's documentation, despite Google always sending me to an old version every single time (get on top of your SEO, Microsoft). That said...
Fairly recently, I was looking in to controlling a service using C# and while the docs claimed that System.Management was deprecated, I could not find code samples anywhere that did what I needed without using System.Management.
It doesn't seem like it's actually deprecated, and I couldn't find any corroborating claims that System.Management was deprecated, the mention only seems to exist on a single MSDN page. This one, in fact: https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
> Classes in the Microsoft.Management.Infrastructure namespace. (The System.Management namespace is no longer supported). For more information, see WMI .NET Overview.
What exactly does "no longer supported" mean if not deprecated? Why is it still in use if it's not supported? Why don't the System.Management docs mention this at all?
Full disclosure, I'm saying this as a very non-C# guy, so my relative inexperience with that ecosystem is absolutely a factor. But my thinking is that, if you're already a decently skilled programmer, you should at least be able to interpret documentation so long as it's not astoundingly terrible. In this case, there isn't a clear answer to my question, so I'm just left feeling like I'm writing doomed code.
Sorry for the rant. It's a relatively minor gripe, to be sure, but it needs fixing.
No, he means Swift and Objective-C. That's what was, is and will be supported.
On the other hand, Microsoft's API screw-ups are legendary at this point... not even they know what developers should use for Windows apps. I think Windows Phone was recently canceled, so that simplifies things a bit.
And even if there was such a blessed SDK/language combination, they'd probably drop it or rename it next year ;-)
I've found that C++/MFC and C#/WinForms are the one that are stable and actually work over the long term. Our >20 year old app runs a lot of MFC code that is unmodified from that era.
I could go on and on about how bad Apple's developer documentation is. So much stuff is missing an overview document or sample project, so you have documentation on the 10 classes but not how they fit together. Sample code that does exist won't compile on the latest Xcode 1/4 times, especially if it's Swift. I've found code that won't compile even in the Swift language documentation. There's almost never any documentation what can go wrong and why.
These days I prefer Stack Overflow answers to Apple's own documentation since it's more up-to-date
When it comes to macOS, it seems that it simply stoped caring. Especially when it comes to features for their traditional UNIXy user base.
Some examples:
- It took them years to bring back features to Pages (e.g. linked text boxes).
- Keynote now crashes on presentations that worked with older versions of Keynote (e.g. presentations converted with PDFToKeyNote).
- XQuartz still doesn't permit native resolution in windows (meaning HiDPI-capable Gtk3+ are scaled up and blurry).
- Location services steals focus from XQuartz, making X11 applications unusable.
- macOS regularly crashes on my MacBook Pro with two external displays when the display configuration changes (e.g. one display is turned off)).
- I regularly run into a bug where my MacBook Pro does not charge when the adapter is plugged in (even though the status icon shows the charging status). Plugging out and in again fixes this.
- Many basic UNIX utilities are buggy and never updated or fixed. E.g. take grep:
- macOS provides no trivial way to semi-automatically install drivers for Bonjour printers anymore if they support Postscript. Pretty annoying if you need scanner functionality.
- Preview.app/PDF kit have become pretty much useless. E.g. form filling for a lot of work forms does not work correctly any more (it used to work find pre-10.12 or 10.11). And since 10.13 Preview.app crashes all the time while regenerating a PDF document using LaTeX (a use-case that worked fine before), sometimes when zooming. Moreover, going through a slide deck with the arrow keys often makes weird jumps through the slides.
...and I could go on for a while. macOS used to be so far ahead of the curve on the UNIX desktop (and perhaps the desktop in general) that even with all the current deficiencies, macOS is still a reasonable desktop. But it is clear that macOS is now beyond its high point. And if Apple does not lose their 'iOS is the future of the desktop'-blinders, things will only go further downhill.
What makes this even more sour is that Mac prices have gone up a quite a bit. A reasonable MacBook (and not the near-EOL Air) with more than one port and a 256GB SSD starts at 1749 Euro. When I started using a Mac as a student ten years ago, an up-to-date Mac Mini was 500 Euro and a reasonable specced (and upgradable) MacBook was ~1000 Euro.
I think the last Mac Pro and the iMac Pro show the disconnect with their traditional user base. People do not want overpriced works of art. They want a stable macOS. They want an upgradable tower Mac Pro, they want a memory-accessible Mac Mini, they want a MacBook Pro that stops optimizing for thinness but has a larger battery, MagSafe, and perhaps one or two USB 3.0 ports during the transition period.
> they want a MacBook Pro that stops optimizing for thinness but has a larger battery, MagSafe, and perhaps one or two USB 3.0 ports during the transition period.
This is the situation I'm in. I need a new laptop as my MBP (2010) has recently hit the hay, but I'm just putting it off and stalling being of things like this and the massive price increases. Instead of magsafe and useful ports I get touchbar... thanks Apple. Honestly trying to convince myself if I can get by with an alternative laptop with Linux (Windows isn't an option anymore).
I was recently looking at replacing my 13" MacbookPro and comparing laptops that would run Linux. Here are the notes I had in order of most-likely to least likely to choose:
* Dell XPS 13 - camera below screen (looks up your nose, fingers in frame), proprietary battery charger. They recently updated it; replaced SD card reader with microSD, USB 3.0 and power dropped for USB-C
I went with a MacBook Pro because soldered on RAM was standard on most all of them which took the price up within 20-30% of the MacBook Pro. With all of the PC laptops I had concerns about trackpad and general build quality and wasn't confident about battery life or resale value.
Out of the concerns we share I didn't find anything better on the PC side. The Razer Blade Stealth was closest, but with 1 USB-C port that is used for charging isn't reasonable, either. Why would I buy anything with USB-C on it if the only port is already occupied?
It's a sad state of affairs. I use the new MBP with touchbar for work and it's a nice machine except the touchbar and dubious keyboard (I can live with it). I just wish it wasn't so user-hostile and objectively good features like magsafe hadn't disappeared. I've already had my work laptop yanked to the floor multiple times by people because the charging cable is much shorter than previous generations.
I've pretty much been looking at the same list as you but have concerns over build quality / trackpad / random design choices like a webcam pointing up your nose. Not sure what I will do yet, will likely hang on until next refresh and see if there's a new 15mbp without touchbar.
NeXT was never about UNIX, rather about all the other UI/UX.
They only based it on UNIX, because they were going after Sun, and just like Microsoftm, UNIX compatibility was a way to bring software into their world, not to out of it.
Now Apple does not need to use that path any more for their survival nor do they care about servers, what matters are Objective-C and Swift OS APIs, not C ones and very latest version of POSIX CLI utilities.
This is exactly why my MBP has been reduced to a $2700 VNC terminal / web browser / mail client. They screwed up keyboard handling in the built-in VNC client a few releases ago, so it’s failing at the most important of those three use cases.
When it eventually dies, I’ll need a replacement with a decent screen, keyboard and trackpad. Apple used to make those, but not any more.
I’ll probably end up running linux on some well-regarded windows laptop.
What broke about keyboard handling? I use the build-in vnc client often (every other vnc client seems to suck). I have trouble with copy/paste...but that's very common with remote login tools.
I have a newer Mac. I didn't like the keyboard at first and still hear about reliability/repair issues, but going back to the mushy keyboards on an older Mac is weird. What's wrong with Apple's trackpads and screens? Trackpads got larger (and get a lot of rogue input when using Linux/Windows), but work great as ever in macOS.
A personal anecdote: when upgrading my High Sierra to the latest version (security fix to the passwordless root fiasco) macOS automatically made an APFS snapshot of my computer in case something went wrong. This is fine, except the snapshot was never removed.
There was absolutely no documentation on this all happening, let alone any UI indicating it (even in Disk Utility!!!). All I saw initially was ~80GB of space used by mysterious “system files” (according to the system profiler). Except they weren’t files at all, it was all hidden in the file system.
So there was literally no way to diagnose this issue without using poorly documented Apple-proprietary command line utilities. Even fdisk didn’t reveal the issue!
If I, a computer science student, have to spend hours trawling forums to solve what should be a trivial issue, then I don’t know how the hell Apple expects the lowest common denominator to cope.
Apple have been getting worse at producing high quality software, in my opinion. Still Apple delivers higher quality stuff then anyone else, so you don't really have anywhere to go.
I recently got an AppleTV, allowing my to cancel my TV via fiber delivered by my ISP. While I have seen a little weirdness from the AppleTV, is not even close to leave of stupidity seen in the tv-box delivered by my ISP. Apple would pretty much have to send a guy to my house and jam a screwdriver into the AppleTV to hit the low level of quality found in other TV boxes.
From what I’ve heard of Apple TV, it does not compare favorably to a $35 Roku stick.
Point taken about cable tv boxes though. The cable company keeps offering to pay me to put one in my house. I fell for that once. Never again. (It is not worth the closet space or hassle of returning the equipment after a few years.)
Any specifics? I had an older Roku and it was incredibly underpowered, but it did work. Is an AppleTV 6x better? Probably not, but its worked out very well for my needs. With the Roku I wished for a single store to buy/rent tv film I wasn't streaming (I think I mostly used Amazon, but I never have been a fan of their app).
They have literally hundreds of billions of dollars in cash to spend on supporting their products. "Too much to handle" can't explain it. It must be cultural.
Very likely it’s design over function and new features over stability. They need to skip adding whatever their latest “innovation” is for a year and nail down their current systems. These yearly cycles are not giving the teams enough time to qa and bugfix.
I attempted to set up a laptop for my daughter before Xmas with my own admin account and hers as a managed account with parental controls on. We fire it up on Xmas morning and it's forgotten almost everything I set up - in particular the whitelisted apps. I switch to my user, set it all up again, switch back, it's forgotten again. Did some googling and it turns out this bug has been around for at least two years [1][2]. This seems like absolutely fundamental functionality, there are effectively no parental controls as it's unable to remember any of the settings.
Ran into this one at work. We wanted to have a public imac as a simple terminal for clients to use our website and set things up. Nothing that needed to be super secure, basically just to walk them through the interface of our stuff etc if they asked, and that we could leave them alone at without any ability to bork the system.
This ended up being such a crapshoot that we had to buy deepfreeze because even the freaking guest account doesn't consistently work the way it should(or, hasn't worked consistently across versions of OSX over the past few years) and basic things like auto updates of software/the OS kept breaking if someone didn't regularly sign into the admin account.
It turned from a quick project that should have been easy and apple-y with basic security settings and enabling auto updates into something that someone from the team has to grab a checklist and verify once a month. It's a complete joke.
It's worth noting apple literally buys deepfreeze for the systems in their own stores. You'd uh, think that their own functionality in the OS would be able to handle that.
> The installer nukes user accounts that have been around for years to replace them with new user accounts without warning (in this case, _assetcache replaced the intermapper user).
Surely this can't be counted as bug. A system account changing to a new user account that does system things (that no normal user will ever touch) should have no impact on the system at all.
The current releases within the Apple ecosystem are rough. Currently weening myself off of iMessage to reduce the pain of potentially moving outside of the OSX ecosystem.
Apple is basically handing Microsoft a golden ticket. With Windows looking pretty dev friendly these days, there's finally some competition for an OS that's both UI and dev friendly.
Give one of the friendlier linuxes a try. Since you're used to working with a unix-ish environment, it will be pretty familiar. Ubuntu (and Mint) do a great job with their UI. With the quality and diversity of software available, I don't miss OSX at all.
The only caveat: libre Office sucks; I've switched to gdocs instead. Maybe it's a configuration thing, but the alternatives are just so easy now, I hardly bother.
I may give Ubuntu a go again. Having a dual boot system was nice in the past, but I also found myself needing one thing that justified using Windows more. In high school it was Warcraft 3, in college it was powerpoint, Visual C++, plus others.
Now that I don't game as much and get to choose the software I use, Ubuntu might work out.
I do enjoy Apples approach to system UI, though. Windows and Ubuntu have always "made sense" where as OSX makes sense and feels nice. Something weirdly intangible that I didn't understand until I was an OSX user.
Linux audio is pretty disappointing. It took me hours of googling and mucking around to get surround audio over HDMI working for my ubuntu HTPC.
I ended up having to completely disable PulseAudio which means there can't be any desktop sounds at all, but at least the audio works in surround from Kodi now.
Also every time I do an update I need to reinstall Nvidia drivers. Which might also break the fragile audio over HDMI setup, who knows?
I recently started using macos for work. I'm on sierra and every day I get pestered about upgrading to high sierra. Every day I also read a new reason not to do that. Is there any way I can turn it off?
Is there a way to just disable the High Sierra notification? I'd still like to be automatically notified of point releases / security updates to Sierra.
[This is a bit diversionary, but I've often seen your username here and wondered if we went to the same school, or if it's coincidence. You'll recognize my username if so.]
[I don't recognise your username but I have an astonishingly poor memory for names. School was Camberwell Grammar. If correct, my email is username at gmail.]
If you ask Siri now, it thinks next Monday is the 15th.
Tonight’s bug occurred on the Watch. It told me to close my Activity rings like yesterday, even though I closed them several hours earlier.
—-
Update
I wanted to add that Alexa and Google define “next Monday” as I do. I didn’t add that to my blog because the point wasn’t to try and criticize Siri. Ambiguity will always be a problem.
> If you ask Siri now, it thinks next Monday is the 15th.
Not sure about this in English, but in French you could have the same problem with humans. Most people would think of "lundi prochain" as the first Monday that follows today, but some (including me, at least before I moved to a place with a different usage) would think of it as the Monday after that. Some regions have an alternative unambiguous way of saying it, some don't.
So while the situation might not be the same in English (I don't know enough about English regionalisms to say), there are cases where usage is just ambiguous and neither Siri nor anyone can really be sure what you mean, unless they have spent enough time talking with you and paying enough attention to learn about these particularities. I guess it might happen with Siri, but I think it's not there yet (for now it's not going to understand that if you say "no Siri, the 18th of December" then it has to change its conception of "next Monday", but it could be done).
Its generally pretty unambiguous in American English. I've only ever run into people claiming to have an odd way of using this and next differently online.
For everyone else, there is an understood "week's" inserted into the phrase "this Monday" or "next Monday" (that is, they mean this week's Monday, even if it was in the past, and next week's Monday, respectively).
Context cues help as well. The question "what did we talk about this Monday?" is obviously past tense and couldn't be interpreted to be referring to the following Monday. But if someone asked me today "lets plan to meet this Monday", its a nonsensical statement that would require clarification, because Monday was 3 days ago.
I'd say it remains pretty ambiguous. I often have trouble with people saying "next Monday" and I have to ask for clarification every time. My default for "next Monday" is "the next Monday we get to." Sometimes people mean the "NEXT" Monday, not "this coming Monday." Awful.
And I never have considered or heard of the "this week's Monday" "next week's Monday" interpretation, although I guess I've heard people speak this way occasionally.
I was always taught growing up that "next" Monday is the one after "this" Monday which is the first Monday you will encounter moving into the future.
I was surprised as an adult to discover that this is not universally held. Since it's pretty obviously ambiguous, I would expect my voice assistant to ask for clarification on which one I meant, and maybe learn from that if it's the kind of assistant which keeps user profile data (which is probably all of them).
I was taught that there are two interpretations, and therefore it's always a good idea to ask for clarification. At least when interacting with humans.
So, what you said is exactly right: Siri should get clarification. And also when stating things in the form of "next Monday" Siri should clarify what is meant, or just avoid the form altogether by instead saying things similar to "this coming Monday" or "the Monday following this one."
In an ideal world Siri would ask you once then learn your style. I would also like to offer a correction. I don’t want Siri to always ask “Did you mean...”
In German* it depends on the tense of the verb. “On Monday I went to…” refers to the most recent Monday in the past. “On Monday I go to…” refers to the closest Monday in the future. Same for “This Monday…”. “Next Monday” refers to the second closest Monday in the future.
I have seen a few bugs as well, I'm sad to say. Most impactful is that Time Machine no longer works... I don't think there is any step that I have not yet tried, short of meeting personally with the developer of the Time Machine software, an option that I don't think is in the cards.
It never finishes. At any given time what it says differs, but at the moment the pulldown menu says "Backing up: 2 KB of 115.3 MB" and it's not moving. It will move slowly, make some progress, then the rightmost number will creep up. It never gets ahead of whatever is mysteriously changing data on the disk, I'm guessing. Even when I leave it alone and go on vacation for a week without the laptop, with all apps closed and the laptop left running.
Eventually the Time Capsule disk (3TB) fills up, from my 1TB laptop, without ever having finished a backup.
Glad to get ideas, but yes I have tried this. Multiple bugs actually. And submitted 'sudo tmdiagnose' logs with them.
And Genius bar. And phone support, second tier support. And replaced the actual physical device with a brand new one via AppleCare. And then repeated the entire cycle with the new device.
My only serious problem with macOS is keyboard language when switching between apps. It changes the current app's language to the one used by the previous app.
Reported it countless times, had a few email exchanges with Craig Federighi, still unsolved after 13 years.
Can anyone write an app to keep each app's input language? I think the OS part that deals with that is still Carbon...
The only bug I know of that actually annoys me is on the recommended music in the music app, when you click on the artist it redirects you back to the recommended playlist rather than the artist.
I really have had no other problems, which is a rather nice surprise if I'm honest.
I’m glad I’m not the only one that noticed this! It’s a small detail and easy to miss, unless you’re an actual user. It makes me wonder if the engineering team doesn’t use Apple Music as their daily music player.
You can work around it by the way, by tapping on now playing -> triple dot -> album cover -> artist.
> Users (with >500 UIDs) can “disappear” until reboot; e.g. id returns nothing for the user.
And randomly later as well. Every few weeks my terminal will complain it can't run sudo because the user doesn't exist. Reopen the terminal -> everything's fine :(
I really wish Apple would fix its SMB implementation - it's a mess.
I'm accessing an NAS from multiple macs and a PC. The performance and reliability with the PC is flawless when it comes to file transfers, browsing and general access. With the macs it's often uncertain whether finder.app will be able to connect, ask for my credentials again, fail to connect, seem to be connected, but really isn't, requiring a restart of the process, not show the NAS in the sidebar or anything inbetween.
And that's not even touching the subpar performance during transfers and listing of large directories.
Of course the NAS might be to blame but I see the same issues at work with the NAS.
> Since I can’t copy files across the network to synchronize photos with other family members (an incredibly common workflow which Apple still hasn’t supported in any way)
Yes. Photo library handling is still pretty bad on all the popular OSs. Everyone wants to sell cloud products to do this, rather than any kind of "local" sync. One of these days I'll write the application to do this.
One more bug in case Apple is reading this (used to file bugs under Apple's BugReporter but seems like no one is reading them): When you AirPlay a video from iPhone to Apple TV 4th gen, you then can not use the AppleTV Remote hardware to pause and play, as the audio will be lost. All with latest iOS, tvOS.
Another very annoying bug. When you press the Home button with your non-Touch-ID registered finger, an "Enter Passcode" screen will appear. But when you cover that finger let say with a tissue paper and press, nothing happen. So I can not unlock my iPhone 6s when I go jogging as I put the phone in a case with a clear front plastic. Even when I use the AssistiveTouch and place a virtual Home button I get the same bug. But this bug does not occur all the time, probably 80-90% of the time. Did Apple change the TouchID feature to require sensing our flesh in order to work?
> "Americans have an impoverished and immature conception of technology, one that fetishizes innovation as a kind of art and demeans upkeep as mere drudgery."
I remember when Apple introduced Force Touch (now the more politically-correct 3D Touch), and Tim said he used force touch to preview emails "all the time". No you don't dude, no one does. That's the most ridiculous made-for-a-demo feature ever.
(I would happily disable 3d touch completely except for it artificially turns off the camera and flashlight buttons on the home-screen. The feature would be useful if they'd just used it as a shortcut for long press.)
I just upgraded my older 10.12 installation on the Macbook - forget bugs for a moment, the installation of updates is a criminally slow and punishing (time wise) endeavor on the Mac compared to Windows 10. It's like no thought went into it to make it fast at all!
Recently I've spent just a few days with macOS and iOS trying to port a game to iOS and I could add a few bugs to this list. Most of them rather cosmetic and just annoying, but speaking about the quality of the software nevertheless.
Well I spend most of my Android coding with the NDK, and I consider it lacks lots of love.
While some things are understable due to the security issues of using C and C++, having to use JNI to call native libraries on device (Skia, libpng, ...) or C for C++ APIs, feels less understandable.
Or how gdb support is hit-and-miss, depending on device's firmware.
Oh and the fun of combining CMake, ndk-build and Gradle experimental plugin builds.
The tooling is better on iOS indeed (aside of being limited to macOS, which is a major PITA, but thankfully there's ssh and stuff). That's not the point though.
What I meant is the overall quality of implementation, not the system designs themselves, where both have their obvious upsides and downsides. What I mean is that you can't have WebGL context in WebView on iOS without risking crashes when your app goes to the background, because you can't use OpenGL when in the background and Apple's own WebView doesn't respect their own rule on that (which turns out is why AdMob users are often having seemingly random crash reports for their apps, I've learned from googling this issue). What I also mean is that I've found some reproducible UI glitches in Android during a few months of usage, and I've found similar amount of them during a few days of iPhone usage.
It feels messy, even though Apple is in position where it's way easier for them to keep it tidy than in the every-vendor-can-do-anything-they-want-kindergarden of Android. Which is really telling.
Are you using non-apple servers or other devices in your home network? If not, that’s probably the reason of most net related bugs.
Also, do not try to do things manually on Apple machines. Do not “copy files” if you want to sync photos, instead, do it the Apple way. It sucks, but it’s the only way.
It's sad, because I really like their whole infrastructure with iCloud and sync between devices.
I don't know what happened, maybe they just have too many products and operating systems to support.