If there's even a minor bug in the new file system, you can lose all your data.
Once APFS comes to macOS, I'm sure there will be mission critical users that will choose to stay on HFS+ for years to come. They won't switch until APFS has seen lots of real world use.
Sneaking in a file system change in a point update of iOS is really a horrid action by Apple. People will update to get bug fixes not knowing the danger to their data. The change should have been deferred until a major iOS update and a new iPhone model. Those with mission critical needs could then stay behind on an old iOS on an old iPhone.
From what I've read, APFS isn't specifically "optimized" for SSD's, but rather makes use of the fast random access capability of SSD.
HFS and HFS+ were designed in a single threaded era. They were also designed for drives that are slow at random access. Therefore, the directory structures are all one big blob at the start of the disk. (Well, actually several, but they'll start out all together.) Now, in a multi core, multi threaded era, all threads have to wait their turn as a single thread accesses the file system. APFS splits the directories up so multiple threads can access the file system. The downside is that data is scattered around, but on an SSD this doesn't matter.