3 ms·
They're not PDF-based. They take in a JSON spec of their own design and the output seems to be a custom HTML-like view. It auto-reflows [to the chagrin of some
by 52-6F-62 8y ago
They're not PDF-based. They take in a JSON spec of their own design and the output seems to be a custom HTML-like view. It auto-reflows [to the chagrin of some art directors and designers].
They seem to have prioritized readability and accessibility by limiting composition.
https://developer.apple.com/documentation/apple_news/apple_news_format https://developer.apple.com/documentation/apple_news/apple_n...
edit: Some back issues are PDFs. Future issues won't be.
- gnicholas 8y agoIs this the same for magazines? If true, this would be great. I can understand how magazine folks would want to be able to have more control over layout and such, and would therefore prefer PDF.
- 52-6F-62 8y agoYep it’s the same across the board. The main differences involve how you utilize the available components and parameters—like web I guess but with greater restrictions that put the reader first (IMO). You’ve nailed the view of art teams, but they’re generally welcoming in my experience. The challenge is in preventing doubling up their workloads. Edit again!: I can’t speak for every magazine and what Apple might be permitting now. But most are providing at least a simple reader-style view.