We have a new Apple Books reader, and we have no idea how it works.
There are no titles.
It doesn’t even show any images.
And no screenshots.
No one can tell us anything more about it than that it is a “mobile-friendly” app.
But, of course, Apple Books is all about reading.
You can read it on your phone.
You’ll find the same kind of text everywhere.
This is where we get to the part where we have to figure out what to do with this new reader.
This article will tell you what to read.
If you’re interested in Apple Books, you’re probably a reader of this blog.
If not, you should.
If there is one thing that Apple Books does differently than its competitors, it’s in this area.
Apple Books offers no app for reading on your iPhone or iPad.
You read it through your phone, which is the best way to read it.
That’s the way it should be.
But it’s also the way most people use their iPhones.
There’s a good reason for this.
Readers use apps, not books.
And apps are easy to use.
The problem is that reading apps can be frustrating and slow.
Apple has made it so that reading on the iPhone is much faster.
It’s a lot more efficient.
If your device has a screen, the process of reading can be much more enjoyable and intuitive.
For a couple of years, I’ve been using my iPhone to read Apple Books.
It was an improvement over my old Kindle reader, which was slow and error-prone.
But there was still a lot of frustration with it.
My old Kindle would load the entire book before I’d finished it, and it would be a lot harder to navigate the interface.
Apple had a plan for me.
In July, the company launched a beta version of its Apple Books app, and then it released a larger one.
The beta version included support for the new iPad Air and iPad mini.
It also had a full-featured reading mode.
It wasn’t perfect.
But the new version was far faster than the old version.
You could use the app to skim a passage, or skip a chapter.
But if you were reading a large book like The Last Unicorn, the speed was still terrible.
Apple didn’t have a clear idea of what was going to work best for people.
That was partly because the new beta was released so late, and partly because Apple didn, well, not know what the heck to do.
The company started working with the folks at Apple to make a new version.
Apple’s beta testers had already been working on a new reader, but they didn’t know what to expect from the beta.
They didn’t even know if it was compatible with their phones.
Apple eventually got around to releasing the beta, and on December 17th, it released an update that made it more compatible.
The new beta included support and better support for older iPads.
But Apple didn`t tell the public that it had fixed the bugs in the beta reader, or that it was ready to go out into the wild.
There was still confusion.
People had been using the beta for years and years, but there was a lot that hadn’t been explained.
And people didn’t seem to understand the differences between the old beta reader and the new one.
They thought they had to download the new reader to read the books, and so they didn`T.
When people tried to download it, they couldn`t do that.
It simply didn’t work.
So people were confused.
And when people tried it, the bugs kept popping up.
For some, this is the first time they’ve encountered a bug in the new Apple books reader.
That`s why they started posting on the forums to share their experiences.
In a few days, I had an entire thread devoted to the new iOS version of the app, including a thread on the Apple forums, where users posted their own stories.
I even found some people who were willing to give their honest feedback on the new app.
This was the first big test of the new readers new capabilities.
It didn`ve been designed to be perfect.
There were a few bugs, too.
The iPad Air was a little slow to load the new readers reader.
Some users reported that the new books reader sometimes didn`ll show a title at all.
Other users complained that the iPad would freeze for a few seconds while they were reading.
And some users reported they had a hard time finding a chapter of a book.
But these were minor issues, and I wasn`t surprised to find that they weren`t the ones making the biggest difference.
The bigger issue was that Apple hadn`t explained how to read books on a modern device.
And there were still many questions.
What happens if the device is broken?
How does it work on older iPhones and iPads?
How do I find a chapter in a