Slashdot Mirror

Developer and blogger Guilherme Rambo, writing for 9to5Mac: Fellow developer Steve Troughton-Smith recently expressed confidence about some evidence found indicating that Apple is working on new Music, Podcasts, and perhaps Books apps for macOS, to join the new TV app. I've been able to independently confirm that this is true. On top of that, I've been able to confirm with sources familiar with the development of the next major version of macOS -- likely 10.15 -- that the system will include standalone Music, Podcasts, and TV apps, but it will also include a major redesign of the Books app.

The new Books app will have a sidebar similar to the News app on the Mac, it will also feature a narrower title bar with different tabs for the Library, Book Store, and Audiobook Store. On the library tab, the sidebar will list the user's Books, Audiobooks, PDFs and other collections, including custom ones. The new Music, Podcasts, and TV apps will be made using Marzipan, Apple's new technology designed to facilitate the porting of iPad apps to the Mac without too many code changes. Further reading: Steven Troughton-Smith Thinks iTunes Breakup is Nigh (DaringFireball).

Joanna Stern, writing for the Wall Street Journal [the link may be paywalled]: Why is the breaking of my MacBook Air keyboard so insanely maddening? Let's take a trip down Memory Lane.
April 2015: Apple releases the all-new MacBook with a "butterfly" keyboard. In order to achieve extreme thinness, the keys are much flatter than older generations but the butterfly mechanism underneath, for which the keyboard is named, aims to replicate the bounce of a more traditional keyboard.
October 2016: The MacBook Pro arrives with a second-generation butterfly keyboard. A few months later, some begin to report that letters or characters don't appear, that keys get stuck or that letters unexpectedly repeat.
June 2018: Apple launches a keyboard repair program for what the company says is a "small percentage" of MacBook and MacBook Pro keyboards impacted.
July 2018: Apple releases a new high-end MacBook Pro with the third-generation of the keyboard that's said to fix the issues.
October 2018: Apple's new MacBook Air also has the third-generation keyboard. I recommend it, and even get one for myself.

Which brings us to the grand year 2019 and my MacBook Air's faulty E and R keys. Others have had problems with Apple's latest laptops, too. A proposed nationwide class-action suit alleges that Apple has been aware of the defective nature of these keyboards since 2015 yet sold affected laptops without disclosing the problem. "We are aware that a small number of users are having issues with their third-generation butterfly keyboard and for that we are sorry," an Apple spokesman said in a statement. "The vast majority of Mac notebook customers are having a positive experience with the new keyboard." If you have a problem, contact Apple customer service, he added. John Gruber, a long time Apple columnist: I consider these keyboards the worst products in Apple history. MacBooks should have the best keyboards in the industry; instead they're the worst. They're doing lasting harm to the reputation of the MacBook brand.

Apple's $29 battery replacement program may have seriously dinged sales of its 2018 iPhone models. From a report: The company replaced 11 million iPhone batteries under the program, John Gruber of tech-focused blog DaringFireball reported Monday, citing Apple CEO Tim Cook at an all-hands meeting. Typically, the company replaces 1 million to 2 million batteries each year, DaringFireball noted. Cook cited the program's negative impact on Apple's revenue in a Jan. 2 sales warning to investors but didn't offer specific numbers.

Fred Imbert, writing for CNBC: Larry Kudlow, director of the National Economic Council, said Friday that Apple's technology may have been stolen by the Chinese. "I don't want to surmise too much here, but Apple technology may have been picked off by China and now China is becoming very competitive with Apple. You've got to have rule of law," Kudlow said in an interview with Bloomberg. "There are some indications from China that they're looking at that, but we don't know that yet. There's no enforcement; there's nothing concrete." Kudlow's comments came shortly after China's Commerce Ministry said Chinese and U.S. officials will meet next week to discuss trade. Both countries have been engaged in a trade spat for months that has sent ripples through global markets. John Gruber at DaringFireball comments: I think what he's saying here is that the Chinese stole Apple technology, copied it, and are now flooding the Chinese market with phones based on that stolen tech. I'm 99.8 percent certain that hasn't happened -- if there were Chinese phones built with stolen Apple technology we'd know it because we'd see it.

Glenn Fleishman, writing for MacWorld: It seems like it was only yesterday that I first used BareBones Software's BBEdit, but in actuality, yesterday is so far away -- 25 years, in fact. With all the twists and turns across more than two decades of Apple as a company, Mac hardware, and the underlying operating system, you might think that BBEdit stands alone as a continuously-developed app shepherded largely or exclusively by the same independent developer -- an app without a giant company behind it. As it turns out, BBEdit is one of several apps that's been around the block more than a few times.

The longevity of indie apps is more extraordinary when you consider the changes Apple put the Mac through from the early 1990s to 2018. Apple switched from Motorola 680x0 processors to PowerPC to Intel chips, from 32-bit to 64-bit code, and among supported coding languages. It revved System 7 to 8 to 9, then to Unix across now 15 major releases (from 10.0 to 10.14). That's a lot for any individual programmer or small company to cope with. Bare Bones's head honcho, Rich Siegel, and the developers behind three other long-running Mac software programs shared with me their insight on development histories for over 25 years, what's changed the most during that time, and any hidden treasures users haven't yet found. You can hear more on BareBones Software's in this recent episode of The Talk Show, a podcast by DaringFireball's John Gruber.

SwiftOnSecurity, regarding Microsoft's switch to Chromium as Windows's built-in rendering engine: This isn't about Chrome. This is about ElectronJS. Microsoft thinks EdgeHTML cannot get to drop-in feature-parity with Chromium to replace it in Electron apps, whose duplication is becoming a significant performance drain. They want to single-instance Electron with their own fork. Electron is a cancer murdering both macOS and Windows as it proliferates. Microsoft must offer a drop-in version with native optimizations to improve performance and resource utilization. This is the end of desktop applications. There's nowhere but JavaScript. John Gruber of DaringFireball: I don't share the depth of their pessimism regarding native apps, but Electron is without question a scourge. I think the Mac will prove more resilient than Windows, because the Mac is the platform that attracts people who care. But I worry. In some ways, the worst thing that ever happened to the Mac is that it got so much more popular a decade ago. In theory, that should have been nothing but good news for the platform -- more users means more attention from developers. The more Mac users there are, the more Mac apps we should see.

The problem is, the users who really care about good native apps -- users who know HIG violations when they see them, who care about performance, who care about Mac apps being right -- were mostly already on the Mac. A lot of newer Mac users either don't know or don't care about what makes for a good Mac app.

SwiftOnSecurity, regarding Microsoft's switch to Chromium as Windows's built-in rendering engine: This isn't about Chrome. This is about ElectronJS. Microsoft thinks EdgeHTML cannot get to drop-in feature-parity with Chromium to replace it in Electron apps, whose duplication is becoming a significant performance drain. They want to single-instance Electron with their own fork. Electron is a cancer murdering both macOS and Windows as it proliferates. Microsoft must offer a drop-in version with native optimizations to improve performance and resource utilization. This is the end of desktop applications. There's nowhere but JavaScript. John Gruber of DaringFireball: I don't share the depth of their pessimism regarding native apps, but Electron is without question a scourge. I think the Mac will prove more resilient than Windows, because the Mac is the platform that attracts people who care. But I worry. In some ways, the worst thing that ever happened to the Mac is that it got so much more popular a decade ago. In theory, that should have been nothing but good news for the platform -- more users means more attention from developers. The more Mac users there are, the more Mac apps we should see.

The problem is, the users who really care about good native apps -- users who know HIG violations when they see them, who care about performance, who care about Mac apps being right -- were mostly already on the Mac. A lot of newer Mac users either don't know or don't care about what makes for a good Mac app.

An anonymous reader writes: Over at DIYPhotography (which we spotted via Daring Fireball), writer and photographer Dunja Djudjic says that she caught Samsung Malaysia using one of her photos to advertise the portrait mode capabilities of the Galaxy A8 Star, a midrange phone that came out over the summer. Djudjic suspects that Samsung licensed the picture from her through the photo site EyeEm, so payment isn't necessarily a problem. But Djudjic does say that the photo wasn't taken with an A8 Star. Instead, it was taken with an (unnamed) DSLR she owns.

Samsung doesn't state outright that the photo was taken on the A8 Star, but it's certainly implied by the page it's on, which is meant to illustrate the phone's capabilities. The page doesn't note that the images are simulated, and after showing Djudjic's photo, it proceeds to show the A8's dual rear cameras, implying a connection.

After years of waiting for someone to design an ARM server processor that could work at scale on the cloud, Amazon Web Services just went ahead and designed its own. From a report: Vice president of infrastructure Peter DeSantis introduced the AWS Graviton Processor Monday night, adding a third chip option for cloud customers alongside instances that use processors from Intel and AMD. The company did not provide a lot of details about the processor itself, but DeSantis said that it was designed for scale-out workloads that benefit from a lot of servers chipping away at a problem. The new instances will be known as EC2 A1, and they can run applications written for Amazon Linux, Red Hat Enterprise Linux, and Ubuntu. They are generally available in four regions: US East (Northern Virginia), US East (Ohio), US West (Oregon), and Europe (Ireland). Intel dominates the market for server processors, both in the cloud and in the on-premises server market. AMD has tried to challenge that lead over the years with little success, although its new Epyc processors have been well-received by server buyers and cloud companies like AWS. John Gruber of DaringFireball, where we first spotted this story, adds: Makes you wonder what the hell is going on at Intel and AMD -- first they missed out on mobile, now they're missing out on the cloud's move to power-efficient ARM chips.

Long-time Slashdot reader kwelch007 writes: I finally gave in, after years of Android loyalty, because the iPhone and Apple Watch just worked, so I was told (and it is true). I changed from my Motorola Maxx for an iPhone 7, because I wanted the Apple Watch. Shortly after, I purchased a second-hand Apple Watch Series 1. I have never looked back...and I'm happy with it.

Last week, I was able to buy an Apple Watch Series 4 with the exact specs I wanted... Wow! The screen is a ton bigger than my Series 1. I noticed right away when it asked me to set my passcode...the buttons were WAY bigger! It truly has the "side-to-side" screen...it's noticable... "Walkie Talkie" is super convenient (used with my associate who told me that it was in stock at Best Buy...)

Cool:

1) It's big, but not much bigger on your wrist than the 42mm versions previous...rather, the screen is bigger, brighter, and more usable.
2) The speakers and mics are far and away better than previous versions of the Apple Watch.
But they don't yet have access to "the highly-touted 'ECG' capability". (Fortune reports it was only approved by America's FDA the day before the launch event -- and isn't yet available for "international" customers.) And the software also isn't ready yet for "Fall Protection," a feature which calls emergency responders if it detects that you've fallen to the ground and you don't respond to prompts for the next 60 seconds. ("The feature is automatic with Watch owners who identify themselves as 65 and up," USA Today reported last week.)

"I spoke to several people in their 40s or 50s who said the same thing: they were already considering buying Series 4 watches for their parents for this feature alone," reported Daring Fireball, and both sites concluded that excitement was actually higher for Apple's new watches than it was for their new iPhones. ("We're talking about a device used by over a billion people -- the iPhone," writes USA Today, "compared with an accessory that analysts say have sold about 15 million units.") Daring Fireball acknowledges that the Apple Watch isn't the "nicest" watch in the world, but it's definitely the nicest if you compare it only to other smart watches and fitness trackers. (Though "that's like saying you're the richest person in the poorhouse.") But what do Slashdot readers think?

Is anyone considering an Apple Watch 4?

Long-time Slashdot reader kwelch007 writes: I finally gave in, after years of Android loyalty, because the iPhone and Apple Watch just worked, so I was told (and it is true). I changed from my Motorola Maxx for an iPhone 7, because I wanted the Apple Watch. Shortly after, I purchased a second-hand Apple Watch Series 1. I have never looked back...and I'm happy with it.

Last week, I was able to buy an Apple Watch Series 4 with the exact specs I wanted... Wow! The screen is a ton bigger than my Series 1. I noticed right away when it asked me to set my passcode...the buttons were WAY bigger! It truly has the "side-to-side" screen...it's noticable... "Walkie Talkie" is super convenient (used with my associate who told me that it was in stock at Best Buy...)

Cool:

1) It's big, but not much bigger on your wrist than the 42mm versions previous...rather, the screen is bigger, brighter, and more usable.
2) The speakers and mics are far and away better than previous versions of the Apple Watch.
But they don't yet have access to "the highly-touted 'ECG' capability". (Fortune reports it was only approved by America's FDA the day before the launch event -- and isn't yet available for "international" customers.) And the software also isn't ready yet for "Fall Protection," a feature which calls emergency responders if it detects that you've fallen to the ground and you don't respond to prompts for the next 60 seconds. ("The feature is automatic with Watch owners who identify themselves as 65 and up," USA Today reported last week.)

"I spoke to several people in their 40s or 50s who said the same thing: they were already considering buying Series 4 watches for their parents for this feature alone," reported Daring Fireball, and both sites concluded that excitement was actually higher for Apple's new watches than it was for their new iPhones. ("We're talking about a device used by over a billion people -- the iPhone," writes USA Today, "compared with an accessory that analysts say have sold about 15 million units.") Daring Fireball acknowledges that the Apple Watch isn't the "nicest" watch in the world, but it's definitely the nicest if you compare it only to other smart watches and fitness trackers. (Though "that's like saying you're the richest person in the poorhouse.") But what do Slashdot readers think?

Is anyone considering an Apple Watch 4?

Two separate reports are saying Apple's yet-to-be-released AirPower charger is facing overheating issues. The product, designed to simultaneously charge an iPhone, Apple Watch, and AirPods, was announced more than a year ago at Apple's 2017 iPhone event. Apple has yet to provide any additional information on AirPower, even during its iPhone event last week. The company even appears to have wiped all mention of it from its website. CNBC reports: Tech writer Sonny Dickson, who has a track record of accurately reporting on Apple, said over the weekend that Apple has struggled with heat management, which affects accuracy and charging speed. Dickson thinks it's unlikely Apple will make its end-of-year release deadline. Daring Fireball's John Gruber said something similar. Gruber said the charging pad, which uses a multi-coil design, is "getting too hot -- way too hot."

"There are engineers who looked at AirPower's design and said it could never work, thermally. ... I think they've either had to go completely back to the drawing board and start over with an entirely different design, or they've decided to give up and they just don't want to say so," Gruber said. Apple gave a broad timeline for AirPower's launch, saying it would go on sale in 2018. So it is still possible it can work out any issues before the end of the year.

According to reliable analyst Ming-Chi Kuo, Apple's next iPad Pro will be switching from the Lightning Port to USB-C for the first time. It will also ship with a new 18W USB-C charger. 9to5Mac reports: While Kuo's memo mentions both the new iPad Pro with USB-C (wow) and MacBook with Touch ID, it's still unclear at this point if we'll see the iPad and Mac on stage at Wednesday's event, or if the September 12 date will be dedicated to iPhone and Apple Watch. That would be a massive change for an iOS device but one that could improve the iPad accessory ecosystem -- and be a boon for productivity. Kuo's memo does not suggest that this is simply a change from USB-A Lightning to USB-C Lightning but instead an actual port change on the iPad itself. Daring Fireball's John Gruber notes that if Kuo is correct, "someone with a Mac, iPhone, and iPad would need three different headphone adapters." That takes courage, Apple...

Black Pixel, which acquired popular Mac RSS reader app NetNewsWire in 2011, announced this week that the brand name is returning to the founder Brent Simmons. From the announcement: Since acquiring NetNewsWire from Newsgator in 2011, we've invested a great deal in the continued development and support of the product suite including the addition of a free sync service. Unfortunately, the ongoing cost of support and feature development for these products require more dedicated resources than we are able to provide. With that in mind, today we are removing all versions of the app from sale. We'll continue to run the sync service for another 60 days, then take it offline at the end of October. Brent Simmons, who founded the app, shared what he plans to do with the brand name: [...] I want to thank them [Black Pixel] for a second thing: their incredible generosity in bringing it back to me. When I asked them about it, they told me they'd already been discussing it. There was never a need to convince them: they thought it was the right thing to do before I even said a word.

[...] You probably know that I've been working on a free and open source reader named Evergreen. Evergreen 1.0 will be renamed NetNewsWire 5.0 -- in other words, I've been working on NetNewsWire 5.0 all this time without knowing it! It will remain free and open source, and it will remain my side project. (By day I'm a Marketing Human at The Omni Group, and I love my job.) Black Pixel will stop selling their versions of the app, and will turn off the syncing system and end customer support -- all of which is detailed in their announcement. (Important note: I will not get any customer data from them, nor will I be doing support for Black Pixel's NetNewsWire.)

I want one thing: to make the very best versions of NetNewsWire ever made. And, along the way, I'd love to have your help. Nothing to Download Yet I don't actually have an app bearing the name NetNewsWire ready to download yet. I will have test versions ready soon, though. It's still going to be a while before the final version of 5.0 ships. The Mac community has been thrilled about the announcement. Daniel Jalkut, founder of blogging tool MarsEdit, said, "I appreciate Black Pixel's decision to return NetNewsWire to Brent Simmons. It was the right move strategically, but also very humanistic." Federico Viticci, a prolific blogger on Apple ecosystem, said, "Congrats Brent Simmons on bringing NetNewsWire home. The Mac can use a modern RSS reader that can stand the test of time." John Gruber, a columnist on Apple ecosystem, said, "Black Pixel did a great job taking over NetNewsWire, but times change, and companies change. Handing the NetNewsWire name back to Brent was a classy move, but completely unsurprising to me, knowing George and the other folks at Black Pixel."

Doug Field, the former VP of Mac hardware who left Apple to become Tesla's chief vehicle engineer, has returned to Cupertino. Field is reportedly working on the company's secretive "Project Titan" self-driving car program. The Verge reports: Field ran Tesla's vehicle production and engineering, but CEO Elon Musk took over responsibility for production this year after the company failed to meet its initial first-quarter goal for the Model 3. Field then took a leave of absence in May, and subsequently left the company altogether in June. Project Titan has reportedly been scaled back considerably from its initial scope, with hundreds of people leaving the division as Apple is said to focus on seeking carmaker partners for its self-driving software. [Daring Fireball's John Gruber] speculates that Field's return to Titan suggests Apple could still have an interest in producing vehicles itself, while cautioning that employees do move between the two companies regularly.

In a story earlier this week, Popular Science magazine explored an age-old topic: Do people need to safely eject a USB stick before they pull it from their computer? The magazine's take on it -- which is, as soon any ongoing transfer of files is complete, it is safe to yank out the flash drive -- has unsurprisingly stirred a debate. Here's what the magazine wrote: But do you really need to eject a thumb drive the right way? Probably not. Just wait for it to finish copying your data, give it a few seconds, then yank. To be on the cautious side, be more conservative with external hard drives, especially the old ones that actually spin. That's not the official procedure, nor the most conservative approach. And in a worst-case scenario, you risk corrupting a file or -- even more unlikely -- the entire storage device. To justify its rationale, the magazine has cited a number of computer science professors. In the same story, however, a director of product marketing at SanDisk made a case for why people should probably safely eject the device. He said, "Failure to safely eject the drive may potentially damage the data due to processes happening in the system background that are unseen to the user."

John Gruber of DaringFireball (where we originally spotted the story), makes a case for why users should safely eject the device before pulling it out: This is terrible advice. It's akin to saying you probably don't need to wear a seat belt because it's unlikely anything bad will happen. Imagine a few dozen people saying they drive without a seat belt every day and nothing's ever gone wrong, so it must be OK. (The breakdown in this analogy is that with seat belts, you know instantly when you need to be wearing one. With USB drives, you might not discover for months or years that you've got a corrupt file that was only partially written to disk when you yanked the drive.)

I see a bunch of "just pull out the drive and not worry about it" Mac users on Twitter celebrating this article, and I don't get it. On the Mac you have to do something on screen when you eject a drive. Either you properly eject it before unplugging the drive -- one click in the Finder sidebar -- or you need to dismiss the alert you'll get about having removed a drive that wasn't properly ejected. Why not take the course of action that guarantees data integrity? What are your thoughts on this? Do you think the answer varies across different file systems and operating systems?

From a story on Digg, via DaringFireball: Magic Leap, the secretive augmented reality company that has raised $2.3 billion, finally demoed its long-rumored, much-vaunted headset on Wednesday (and announced that the headset will ship this summer). It was disappointing. Magic Leap has promised big things -- remember the tiny elephant in your hands? Remember that whale jumping out of the gym floor? But the animations demonstrated on Wednesday fall short of those promises. Waaaay short. An executive with Magic Leap, which has long remained tight lipped on its roadmap and commercial availability of its products, said on a Twitch livestream this week that the Magic Leap One, a developer-geared headset, will ship this season. (Summer ends September 22, so the company has 10 weeks to meet its self-imposed deadline.)

An anonymous reader writes: Tech blogger John Gruber appears to have successfully identified one of the restaurants mentioned in a post on Google's AI blog that bragged about "a meal booked through a call from Duplex." Mashable then asked a restaurant employee there if Google had let him know in advance that they'd be receiving a call from their non-human personal assistant AI. "No, of course no," he replied. And "When I asked him to confirm one more time that Duplex had called...he appeared to get nervous and immediately said he needed to go. He then hung up the phone."

John Gruber now asks: "How many real-world businesses has Google Duplex been calling and not identifying itself as an AI, leaving people to think they're actually speaking to another human...? And if 'Victor' is correct that Hong's Gourmet had no advance knowledge of the call, Google may have violated California law by recording the call." Friday he added that "This wouldn't send anyone to prison, but it would be a bit of an embarrassment, and would reinforce the notion that Google has a cavalier stance on privacy (and adhering to privacy laws)."
The Mercury News also reports that legal experts "raised questions about how Google's possible need to record Duplex's phone conversations to improve its artificial intelligence may come in conflict with California's strict two-party consent law, where all parties involved in a private phone conversation need to agree to being recorded."

For another perspective, Gizmodo's senior reviews editor reminds readers that "pretty much all tech demos are fake as hell." Speaking of Google's controversial Duplex demo, she writes that "If it didn't happen, if it is all a lie, well then I'll be totally disappointed. But I can't say I'll be surprised."

An anonymous reader writes: Tech blogger John Gruber appears to have successfully identified one of the restaurants mentioned in a post on Google's AI blog that bragged about "a meal booked through a call from Duplex." Mashable then asked a restaurant employee there if Google had let him know in advance that they'd be receiving a call from their non-human personal assistant AI. "No, of course no," he replied. And "When I asked him to confirm one more time that Duplex had called...he appeared to get nervous and immediately said he needed to go. He then hung up the phone."

John Gruber now asks: "How many real-world businesses has Google Duplex been calling and not identifying itself as an AI, leaving people to think they're actually speaking to another human...? And if 'Victor' is correct that Hong's Gourmet had no advance knowledge of the call, Google may have violated California law by recording the call." Friday he added that "This wouldn't send anyone to prison, but it would be a bit of an embarrassment, and would reinforce the notion that Google has a cavalier stance on privacy (and adhering to privacy laws)."
The Mercury News also reports that legal experts "raised questions about how Google's possible need to record Duplex's phone conversations to improve its artificial intelligence may come in conflict with California's strict two-party consent law, where all parties involved in a private phone conversation need to agree to being recorded."

For another perspective, Gizmodo's senior reviews editor reminds readers that "pretty much all tech demos are fake as hell." Speaking of Google's controversial Duplex demo, she writes that "If it didn't happen, if it is all a lie, well then I'll be totally disappointed. But I can't say I'll be surprised."

HTC has begun to ramp up marketing campaign for its next major smartphone release, teasing that they will be making a proper announcement on May 23rd. From a report: In an email sent to the press this morning and posted on their website, HTC posted a photo of neatly laid out phone components, with the text "Coming Soon... A phone that is more than the sum of its specs." The photo and the announcement give a May 23rd date for more details. AnandTech has added an update to the story, (Via DaringFireball ): As pointed out by a reader, these aren't new components. Or even components of an HTC phone. Rather they're a disassembled iPhone 6...

John Gruber, reporting for DaringFireball: It's natural to speculate how a bug as egregious as the now-fixed High Sierra root login bug could escape notice for so long. It seems to have been there ever since High Sierra 10.3.0 shipped on September 25, and may have existed in the betas through the summer. One explanation is that logging in with the username "root" and a blank password is so bizarre that it's the sort of thing no one would think to try. More insidious though, is the notion that it might not have escaped notice prior to its widespread publicization yesterday -- but that the people who had heretofore discovered it kept it to themselves. This exploit was in fact posted to Apple's own support forums on November 13. It's a bizarre thread. The thread started back on June 8 when a user ran into a problem after installing the WWDC developer beta of High Sierra.

Details of new iPhones and other forthcoming Apple devices have been revealed via an apparent leak. From a report: Two news sites were given access to an as-yet-unreleased version of the iOS operating system. The code refers to an iPhone X in addition to two new iPhone 8 handsets. It also details facial recognition tech that acts both as an ID system and maps users' expressions onto emojis. One tech writer said it was the biggest leak of its kind to hit the firm. [...] "As best I've been able to ascertain, these builds were available to download by anyone, but they were obscured by long, unguessable URLs [web addresses]," wrote John Gruber, a blogger known for his coverage of Apple. "Someone within Apple leaked the list of URLs to 9to5Mac and MacRumors. I'm nearly certain this wasn't a mistake, but rather a deliberate malicious act by a rogue Apple employee." Neither Mr Gruber nor the two Apple-related news sites have disclosed their sources. However, the BBC has independently confirmed that an anonymous source provided the publications with links to iOS 11's golden master (GM) code that downloaded the software from Apple's own computer servers. It's a big blow to Apple, which uses surprise as a key element at its events. The leak could take some wind out of its sails as it looks to wow consumers. In 2012, Tim Cook had said the company was planning to "double down on secrecy." At the quarterly earnings call, he blamed the leaks about the upcoming iPhone models as one of the reasons that slowed down the sales of current generation iPhone models. However, an analysis published over the weekend found that Apple itself has been the source of several of these leaks in the years since. Earlier this year, the company held a meeting to boast about its internal progress to curb leaks. The hour-long recording of the meeting ironically got leaked. Nearly all details, except the final press renders of the new iPhone models, have leaked. In a subsequent post, Gruber wrote: The BBC doesn't say definitively that the leak was sent by an Apple employee, but I can state with nearly 100 percent certainty that it was. I also think there's a good chance Apple is going to figure out who it was. [...] That person should be ashamed of themselves, and should be very worried when their phone next rings. Moments ago, 9to5Mac reported about a new tvOS firmware leak, which appeared "to be out in the wild today" that details the upcoming features of the next generation Apple TV streaming device.

Details of new iPhones and other forthcoming Apple devices have been revealed via an apparent leak. From a report: Two news sites were given access to an as-yet-unreleased version of the iOS operating system. The code refers to an iPhone X in addition to two new iPhone 8 handsets. It also details facial recognition tech that acts both as an ID system and maps users' expressions onto emojis. One tech writer said it was the biggest leak of its kind to hit the firm. [...] "As best I've been able to ascertain, these builds were available to download by anyone, but they were obscured by long, unguessable URLs [web addresses]," wrote John Gruber, a blogger known for his coverage of Apple. "Someone within Apple leaked the list of URLs to 9to5Mac and MacRumors. I'm nearly certain this wasn't a mistake, but rather a deliberate malicious act by a rogue Apple employee." Neither Mr Gruber nor the two Apple-related news sites have disclosed their sources. However, the BBC has independently confirmed that an anonymous source provided the publications with links to iOS 11's golden master (GM) code that downloaded the software from Apple's own computer servers. It's a big blow to Apple, which uses surprise as a key element at its events. The leak could take some wind out of its sails as it looks to wow consumers. In 2012, Tim Cook had said the company was planning to "double down on secrecy." At the quarterly earnings call, he blamed the leaks about the upcoming iPhone models as one of the reasons that slowed down the sales of current generation iPhone models. However, an analysis published over the weekend found that Apple itself has been the source of several of these leaks in the years since. Earlier this year, the company held a meeting to boast about its internal progress to curb leaks. The hour-long recording of the meeting ironically got leaked. Nearly all details, except the final press renders of the new iPhone models, have leaked. In a subsequent post, Gruber wrote: The BBC doesn't say definitively that the leak was sent by an Apple employee, but I can state with nearly 100 percent certainty that it was. I also think there's a good chance Apple is going to figure out who it was. [...] That person should be ashamed of themselves, and should be very worried when their phone next rings. Moments ago, 9to5Mac reported about a new tvOS firmware leak, which appeared "to be out in the wild today" that details the upcoming features of the next generation Apple TV streaming device.

On Tuesday, ZDNet reported that popular weather app AccuWeather was sending location-identifying information to a monetization firm, even when a person had disabled location data from the app. In a response, AccuWeather said today "if a user opts out of location tracking on AccuWeather, no GPS coordinates are collected or passed without further opt-in permission from the user." But it is misleading people. John Gruber of DaringFireball writes: The accusation has nothing to do with "GPS coordinates." The accusation is that their iOS app is collecting Wi-Fi router names and MAC addresses and sending them to servers that belong to Reveal Mobile, which in turn can easily be used to locate the user. Claiming this is about GPS coordinates is like if they were caught stealing debit cards and they issued a denial that they never stole anyone's cash. The accusation comes from Will Strafech, a respected security researcher who discovered the "actual information" by observing network traffic. He saw the AccuWeather iOS app sending his router's name and MAC address to Reveal Mobile. This isn't speculation. They were caught red-handed. GPS information is more precise, and if you grant the AccuWeather app permission to access your location (under the guise of showing you local weather wherever you are, as well as localized weather alerts), that more precise data is passed along to Reveal Mobile as well. But Wi-Fi router information can be used to locate you within a few meters using publicly available databases. Seriously, go ahead and try it yourself: plug your Wi-Fi router's BSSID MAC address into this website, and there's good chance it'll pinpoint your location on the map. "Other data, such as Wi-Fi network information that is not user information, was for a short period available on the Reveal SDK, but was unused by AccuWeather," the company writes. In what way is the name and MAC address of your router not "user information"? And saying the information was "unused by AccuWeather" is again sleight of hand. The accusation is not that AccuWeather itself was using the location of the Wi-Fi router, but that Reveal Mobile was. Here are Reveal Mobile's own words about how they use location data.

Favicon -- or its lack thereof, to be precise -- has remained one of the longest running issues Safari users have complained about. For those of you who don't use Safari, just have a look at this mess I had earlier today when I was using Safari on a MacBook. There's no way I can just have a look at the tabs and make any sense of them. John Gruber, writing for DaringFireball: The gist of it is two-fold: (1) there are some people who strongly prefer to see favicons in tabs even when they don't have a ton of tabs open, simply because they prefer identifying tabs graphically rather than by the text of the page title; and (2) for people who do have a ton of tabs open, favicons are the only way to identify tabs. With many tabs open, there's really nothing subjective about it: Chrome's tabs are more usable because they show favicons. [...] Once Safari gets to a dozen or so tabs in a window, the left-most tabs are literally unidentifiable because they don't even show a single character of the tab title. They're just blank. I, as a decade-plus-long dedicated Safari user, am jealous of the usability and visual clarity of Chrome with a dozen or more tabs open. And I can see why dedicated Chrome users would consider Safari's tab design a non-starter to switching. I don't know what the argument is against showing favicons in Safari's tabs, but I can only presume that it's because some contingent within Apple thinks it would spoil the monochromatic aesthetic of Safari's toolbar area. [...] And it's highly debatable whether Safari's existing no-favicon tabs actually do look better. The feedback I've heard from Chrome users who won't even try Safari because it doesn't show favicons isn't just from developers -- it's from designers too. To me, the argument that Safari's tab bar should remain text-only is like arguing that MacOS should change its Command-Tab switcher and Dock from showing icons to showing only the names of applications. The Mac has been famous ever since 1984 for placing more visual significance on icons than on names. The Mac attracts visual thinkers and its design encourages visual thinking. So I think Safari's text-only tab bar isn't just wrong in general, it's particularly wrong on the Mac.

John Gruber, writing for DaringFireball: The single biggest misconception about iOS is that it's good digital hygiene to force quit apps that you aren't using. The idea is that apps in the background are locking up unnecessary RAM and consuming unnecessary CPU cycles, thus hurting performance and wasting battery life. That's not how iOS works. The iOS system is designed so that none of the above justifications for force quitting are true. Apps in the background are effectively "frozen", severely limiting what they can do in the background and freeing up the RAM they were using. iOS is really, really good at this. It is so good at this that unfreezing a frozen app takes up way less CPU (and energy) than relaunching an app that had been force quit. Not only does force quitting your apps not help, it actually hurts. Your battery life will be worse and it will take much longer to switch apps if you force quit apps in the background. [...] In fact, apps frozen in the background on iOS unfreeze so quickly that I think it actually helps perpetuate the myth that you should force quit them: if you're worried that background apps are draining your battery and you see how quickly they load from the background, it's a reasonable assumption to believe that they never stopped running. But they do. They really do get frozen, the RAM they were using really does get reclaimed by the system, and they really do unfreeze and come back to life that quickly.

As we near the launch of the next iPhone, rumors are swirling about what it may feature. One of the most recent reports comes from developer and blogger John Gruber, who claims the iPhone 8 will have a starting price of around $1200. 9to5Mac reports: He last week said that he believed that what we've been referring to as the iPhone 8 would be called the iPhone Pro and that he actually hoped it would be really expensive: "I hope the iPhone Pro starts at $1500 or higher. I'd like to see what Apple can do in a phone with a higher price." As you might imagine, that generated quite a bit of discussion. Gruber has backed down somewhat from this position, and is now suggesting a starting point of around $1200: "$1,500 as a starting price is probably way too high. But I think $1,200 is quite likely as the starting price, with the high-end model at $1,300 or $1,400." His argument is effectively that Apple is constrained in what it can do in a phone because any technology included in the phone has to be available in huge volumes. If it were willing to sell fewer at a higher price, then it would have more options. There has been speculation that Gruber may have been tipped by Apple, and using his posts to prepare the ground for what would otherwise be a severe case of sticker shock. But Gruber denied this. If Apple does launch the iPhone 8 with a 4-figure price tag, would you buy it?

As we near the launch of the next iPhone, rumors are swirling about what it may feature. One of the most recent reports comes from developer and blogger John Gruber, who claims the iPhone 8 will have a starting price of around $1200. 9to5Mac reports: He last week said that he believed that what we've been referring to as the iPhone 8 would be called the iPhone Pro and that he actually hoped it would be really expensive: "I hope the iPhone Pro starts at $1500 or higher. I'd like to see what Apple can do in a phone with a higher price." As you might imagine, that generated quite a bit of discussion. Gruber has backed down somewhat from this position, and is now suggesting a starting point of around $1200: "$1,500 as a starting price is probably way too high. But I think $1,200 is quite likely as the starting price, with the high-end model at $1,300 or $1,400." His argument is effectively that Apple is constrained in what it can do in a phone because any technology included in the phone has to be available in huge volumes. If it were willing to sell fewer at a higher price, then it would have more options. There has been speculation that Gruber may have been tipped by Apple, and using his posts to prepare the ground for what would otherwise be a severe case of sticker shock. But Gruber denied this. If Apple does launch the iPhone 8 with a 4-figure price tag, would you buy it?

"Every once in awhile a revolutionary product comes along that changes everything," said co-founder and former Apple CEO Steve Jobs, as he kickstarted the iPhone keynote. Ten years ago, thousands of people around the world listened to him in a mock turtleneck talk about a phone. They liked it so much that they decided to wait outside Apple stores for hours on end to buy one. Little did anyone know the phone -- called the iPhone -- would go on to revolutionize, in the truest sense of the word, the smartphone industry as we know it.

From an Economist article: No product in recent history has changed people's lives more. Without the iPhone, ride-hailing, photo-sharing, instant messaging and other essentials of modern life would be less widespread. Shorn of cumulative sales of 1.2bn devices and revenues of $1trn, Apple would not hold the crown of the world's largest listed company. Thousands of software developers would be poorer, too: the apps they have written for the smartphone make them more than $20bn annually. Here's how some journalists saw the original iPhone. David Pogue, writing for the New York Times: But even in version 1.0, the iPhone is still the most sophisticated, outlook-changing piece of electronics to come along in years. It does so many things so well, and so pleasurably, that you tend to forgive its foibles. Walt Mossberg, writing for the Wall Street Journal: Expectations for the iPhone have been so high that it can't possibly meet them all. It isn't for the average person who just wants a cheap, small phone for calling and texting. But, despite its network limitations, the iPhone is a whole new experience and a pleasure to use. John Gruber's first impressions of the iPhone: The iPhone is 95 percent amazing, 5 percent maddening. I'm just blown away by how nice it is -- very thoughtful UI design and outstanding engineering. It is very fun. Jason Snell, writing for Macworld: To put it more simply: The iPhone is the real deal. It's a product that has already changed the way people look at the devices they carry in their pockets and purses. After only a few days with mine, the prospect of carrying a cellphone with me wherever I go no longer fills me with begrudging acceptance, but actual excitement. Recode has some charts that show how the iPhone has grown over the years. Here's the primer: 1. The iPhone put the internet in everyone's pocket.
2. The iPhone transformed photography from a hobby to a part of everyday life.
3. The iPhone App Store changed the way software was created and distributed.
4. iPhone apps changed everything, even how people work.
5. The iPhone made Apple the world's most valuable company. Apple commentator Horace Dediu writing for Asymco: The iPhone is the best selling product ever, making Apple perhaps the best business ever. Because of the iPhone, Apple has managed to survive to a relatively old age. Not only did it build a device base well over 1 billion it engendered loyalty and satisfaction described only by superlatives. To summarize I can offer two numbers:
1. 1,162,796,000 iPhones sold (to end of March 2017).
2. $742,912,000,000 in revenues. $1 trillion will be reached in less than 18 months. In closing, security researcher Mikko Hypponen tweeted, "iPhone is 10 years old today. After 10 years, not a single serious malware case. It's not just luck; we need to congratulate Apple on this."

Web developer Alex Kras on Monday listed a number of reasons why he dislikes Google's AMP project, and why he pulled support for it on his website. From his post: Back in the day we used to have WAP pages -- specific web pages that were presented only to mobile devices. Opting into AMP, for publishers, is kind of like going back to those days. Instead of using responsive design (making sure that one version of the site works well on all devices) publishers are forced to maintain two versions of each page -- their regular version for larger devices and mobile phones that don't use Google and the AMP version. The benefit of AMP is that it imposes tough restrictions on content, making it load fast. The issue with this approach is that AMP becomes a subset of the original content. For example, user comments are often removed. I also find the way images load in AMP to be buggy. AMP tries to load an image only when it becomes visible to the user, rendering a white square instead of the image. In my experience I've seen it fail fairly regularly, leaving the article with an empty white square instead of the image. [...] It's up to publishers to decide if they want to add AMP support on their site. Users, however, don't have an option to turn AMP off. It would be nice if Google provided a user level setting to turn results rendered as AMP off. Unfortunately, even if they were to add this option, it wouldn't help much when Twitter of Facebook would decide to server AMP. Further reading: Kill Google AMP before it KILLS the web - The Register, The Problem With Google AMP, 2 Billion Pages On Web Now Use Google's AMP, Pages Now Load Twice As Fast. John Gruber on open web: Fuck Facebook.

Dieter Bohn, writing for The Verge: Traditionally, we think of the web as a combination of a set of specific technologies paired with some core philosophical principles. The problem -- the reason this question even matters -- is that there are a lot of potential replacements for the parts of the web that fix what's broken with technology, while undermining the principles that ought to go with it. [...] A lot of tech companies are flailing around looking for ways to fix this problem. There are web apps that work in Chrome but not really all that well elsewhere. There are Instant Articles in Facebook and AMP pages on Google. There are Instant Android apps that stream to your phone over the internet instead of being installed, which go away when you're done with them just like a browser tab. Google claims to be trying to bring some of the open ethos of the web to smart speakers. Hell, go back to 2014 and you'll find Apple pundit John Gruber arguing we should consider apps and "anything transmitted using HTTP and HTTPS" as part of the web. [...] And now, a brief definition of the web: To count as being part of the web, your app or page must: 1. Be linkable, and 2. Allow any client to access it. That's it.

Apple is moving away from the current, cylinder-shaped design used on its Mac Pro desktop, but that replacement will take until next year to hit shelves. From a report: "The Mac Pro, the current vintage that we introduced, we wanted to do something bold and different. In retrospect, it didn't well suit some of the people we wanted to reach," admitted Apple SVP Craig Federighi. "So many of our customers were moving to iMac that we saw a path to address to many, many more of those people," he added. "With the current generation Mac Pro, which some customers love, others may not, one of the things that's certainly clear and true about that is the team tried to do something different, something bold and we always want to encourage the Mac team that whatever products you make, that make customers happy, that we do bold work. Because the Mac's always been about that. It's been about not being conventional thinking, not me-too-stuff," said Phil Schiller. [...] While we'll have to wait until 2018 for the Mac Pro rebirth ("Want to do something great... that will take longer than this year to do," said Schiller), iMac fans can expect a significant update this year, including some new configurations designed specifically for Pro users who already fans of the all-in-one design. [...] Schiller was somewhat less emphatic when I asked if he was willing to make any "courageous" decisions about Mac Pro ports. I thought I saw a little discomfort flicker across Schiller's face as he reacted to that word and he told me that Apple wasn't making promises about ports on the Mac Pro. Port decisions, he said, are made at a product level. "Just because on one product we removed something, doesn't mean we're going to remove it elsewhere," he told me. More on this here.

An employee, who claims to have worked on the development of Flash, writes: Apparently, the world settled on the "One True Cause" for why Flash "died". Take for example this blogpost by John Gruber about FedEx... it ends with this consideration on Steve Jobs' "Thoughts on Flash": "If it had been an angry rant, it would have been easily dismissed without needing to be factually refuted -- "That's just Jobs being a prick again." The fact that it wasn't angry, and because it was all true, made it impossible to refute."

Impossible to refute. There's no doubt that this was the beginning of the end for Flash, right? Except that this is utterly wrong. I worked on Flash, and I worked on the thing that actually killed Flash. It is my strong belief, based on what I observed, that Steve Jobs' letter had little impact in the final decision -- it was really Adobe who decided to "kill" Flash. Yes, Flash was a bad rap for Adobe, and Steve's letter didn't help. But ultimately, what was probably decisive was the fact that developing Flash cost Adobe a ton of money. John Gruber, responding to the blogpost: To be clear, I don't think Jobs's letter killed Flash. But I don't think Adobe did either. Eventually Adobe accepted Flash's demise. What killed Flash was Apple's decision not to support it on iOS, combined with iOS's immense popularity and the lucrative demographics of iOS users. If Jobs had never published "Thoughts on Flash", Flash would still be dead. The letter explained the decision, but the decision that mattered was never to support it on iOS in the first place. It's possible that Flash would have died even if Apple had decided to allow it on iOS. Android tried that, and the results were abysmal. Web page scrolling stuttered, and video playback through Flash Player halved battery life compared to non-Flash playback.

An employee, who claims to have worked on the development of Flash, writes: Apparently, the world settled on the "One True Cause" for why Flash "died". Take for example this blogpost by John Gruber about FedEx... it ends with this consideration on Steve Jobs' "Thoughts on Flash": "If it had been an angry rant, it would have been easily dismissed without needing to be factually refuted -- "That's just Jobs being a prick again." The fact that it wasn't angry, and because it was all true, made it impossible to refute."

Impossible to refute. There's no doubt that this was the beginning of the end for Flash, right? Except that this is utterly wrong. I worked on Flash, and I worked on the thing that actually killed Flash. It is my strong belief, based on what I observed, that Steve Jobs' letter had little impact in the final decision -- it was really Adobe who decided to "kill" Flash. Yes, Flash was a bad rap for Adobe, and Steve's letter didn't help. But ultimately, what was probably decisive was the fact that developing Flash cost Adobe a ton of money. John Gruber, responding to the blogpost: To be clear, I don't think Jobs's letter killed Flash. But I don't think Adobe did either. Eventually Adobe accepted Flash's demise. What killed Flash was Apple's decision not to support it on iOS, combined with iOS's immense popularity and the lucrative demographics of iOS users. If Jobs had never published "Thoughts on Flash", Flash would still be dead. The letter explained the decision, but the decision that mattered was never to support it on iOS in the first place. It's possible that Flash would have died even if Apple had decided to allow it on iOS. Android tried that, and the results were abysmal. Web page scrolling stuttered, and video playback through Flash Player halved battery life compared to non-Flash playback.

Apple said today it will kick off this year's Worldwide Developers Conference on June 5. Much like every year, the developer conference is the place where we can expect to see what's coming to iOS, macOS, watchOS, and tvOS later this year. This year, the event is being held in a different venue: the McEnery Convention Center in San Jose, the original home of WWDC. John Gruber, writing for DaringFireball: First, announcing early really helps people who have to travel long distances to attend, particularly those from outside the U.S. The San Jose Convention Center is the original home of WWDC -- that's where it was held from 1988 through 2002. (WWDC 2002 was the year Steve Jobs held a funeral for Mac OS 9 during the keynote.) San Jose is way closer to Apple headquarters. San Francisco is about an hour drive from 1 Infinite Loop. The San Jose Convention Center is only five minutes away from Apple's new campus. Schiller emphasized to me that this is a big deal: more Apple employees from more teams will be present, simply because they won't have to devote an entire day to being there. (This could be a particular boon to WWDC's developer labs, where attendees can get precious face time with Apple's engineers.)

An anonymous reader shares a blog post: Apple stated that Q1 FY2017 was an all-time record for quarterly revenue. The media dutifully and mostly uncritically spread this "great" news for Apple. Technically the claim is true, the revenue was an all-time record. True but misleading. Although Apple didn't lie as such, you might say there was a sin of omission, and a definite spin of the facts. Most Apple fiscal quarters are 13 weeks long. Once in a while, however, they need a 14 week quarter. You might call it a "leap quarter". There was a good explanation of this financial practice a few years ago in Slate. Apple's Q1 2017 was a 14 week quarter, for the first time since Q1 2013. John Gruber writes at DaringFireball, "Adjusted for the extra week, Apple actually had another down quarter."

At company's quarterly earnings call, Apple CEO Tim Cook said the holiday period was the company's "best quarter ever" for Apple Watch -- both units and revenues -- "with holiday demand so strong that we couldn't make enough." He added: Apple Watch is the best-selling smartwatch in the world, and also the most-loved, with the highest customer satisfaction in its category by a wide margin. Apple Watch is the ultimate device for a healthy life, and it's the gold standard for smartwatches. We couldn't be more excited about Apple Watch. Long time Apple commentator Rene Ritchie writes: There's a strange narrative in the tech community concerning Apple Watch being a flop, a failure, or in some way, shape, or form, a disappointment. It's particularly bizarre given Apple Watch, as part of the wearable market, is doing record numbers. It could be that there is no real "Smartwatch market", just an Apple Watch market. Much like there's no real "tablet market", just an iPad market. Since it's such a new product category and most of the existing products are still bound to phones, it could also simply be too soon to tell.John Gruber adds: I think we should stop talking about "smartwatches" and just consider Apple Watch a "watch", period. In September, Apple claimed watch revenues second only to Rolex. How can it not be considered a hit at this point?

It appears Google recently turned on VP9 codec on YouTube for delivering 4K video. However, because of this, Safari users are unable to watch videos uploaded to the service since early December in full 4K resolution. From a report: Specifically, YouTube appears to be storing video on its servers using either the more efficient VP9 codec or the older H.264 codec. Safari only supports the latter, which explains why recently uploaded 4K videos are only able to be viewed in up to 1440p. Funnily enough, the same videos can be streamed by Safari in native 4K as long as they're embedded in another website, suggesting that the VP9 codec support requirement only applies to videos viewed directly on YouTube's website. Until Apple updates Safari to support the VP9 codec, Mac users who want to access newer 4K video on YouTube in native 2160p resolution are advised to use a different browser.John Gruber of DaringFireball writes, "I'm curious what Google's thinking is here. My guess: a subtle nudge to get more Mac users to switch from Safari to Chrome. 4K playback is going to require H.264 support if they want it to work on iOS, though."

Glenn Fleishman, writing for The Atlantic: Many aspects of website design have improved to the point that nuances and flourishes formerly reserved for the printed page are feasible and pleasing. But there's a seemingly contrary motion afoot with quotation marks: At an increasing number of publications, they've been ironed straight. This may stem from a lack of awareness on the part of website designers or from the difficulty in a content-management system (CMS) getting the curl direction correct every time. It may also be that curly quotes' time has come and gone. Major periodicals have fallen prey, including those with a long and continuing print edition. Not long ago, Rolling Stone had straight quotes in its news-item previews, but educated them for features; the "smart" quotes later returned. Fast Company opts generally for all "dumb" quotes online, while the newborn digital publication The Outline recently mixed straight and typographic in the same line of text at its launch. Even the fine publication you're currently reading has occasionally neglected to crook its pinky.(Via DaringFireball -- John's take on this is insightful.) At Slashdot, we also avoid curly quotes -- and when we miss, you see them as weird characters on the site!

One of the biggest features on iOS that isn't available on Android is iMessage, an instant messaging service that allows users to send information over Wi-Fi, 4G LTE, and other forms of internet access to other iOS or OS X users. Earlier this year, there were been rumors swirling around the possibility of the service coming to Android due to Apple's increased focus on services, "which means opening up certain avenues beyond its own iOS and OS X platforms." Today, Daring Fireball's John Gruber has added fuel to the fire by mentioning that he's "heard from little birdies" that a handful of "detailed mockups" of iMessage for Android have been shared around Apple. MacRumors reports: The user interface of the Android app is said to have gone through numerous designs, from one that looks identical to the version on iOS, to another that has a "pure Material Design," using Google's design language it developed a few years ago. Gruber still thinks iMessage on Android "might happen sooner or later," mainly because of iMessage's new monetized Messages App Store, which could net Apple increased income in its already profitable services category if it translated the app to Android. Apple undoubtedly created mockups for all types of products and services, the vast majority of which never make it to release, and it's unclear exactly how far along the iMessage for Android preliminary designs were at the time of their circulation through Apple, or when exactly that occurred. Still, Gruber notes that while an Android version of iMessage "may never see the light of day," even the existence of such mockups "strongly suggests that there's no 'of course not' to it."

American author and entrepreneur Seth Godin argues that though hardware is nice and dandy, it is the software that matters. And not just software that runs on a computer, "but the metaphorical idea of rules and algorithms designed to solve problems and connect people," he writes. Godin has used the piece to note how Apple has increasingly grown focused on hardware, and as a result, it's not putting much effort to fixing its software. He writes, "Automator, a buggy piece of software with no support, and because it's free, no competitors. Keynote, a presentation program that hasn't been improved in years. iOS 10, which replaces useful with pretty. iTunes, which is now years behind useful tools like Roon. No significant steps forward in word processing, spreadsheets, video editing, file sharing, internet tools, conferencing, etc. Apple contributed mightily to a software revolution a decade ago, but they've stopped. Think about how many leaps forward Slack, Dropbox, Zapier and others have made in popular software over the last few decades. But it requires a significant commitment to keep it moving forward. It means upending the status quo and creating something new." From the article: Software can change faster than hardware, which means that in changing markets, bet on software. It's tempting to treat the user interface as a piece of fashion, some bling, a sort of jewelry. It's not. It's the way your user controls the tool you build. Change it when it stops working, not when you're bored with it. Every time you change the interface, you better have a really good reason.John Gruber disagrees. He writes: Software, in general, is much better than it used to be. Unlike 1995, we don't lose data due to bugs very often. (For me personally, I can't even remember the last time I lost data.) But our hardware is so much better than our software, the contrast is jarring. An iPhone is a nearly perfect object. Sleek, attractive, simple. The hardware is completely knowable -- there are only five buttons, each of them easily understood. iOS, however, is effectively infinite. The deeper our software gets, the less we know and understand it. It's unsettling.

On Thursday, Spotify made major accusations against Apple of playing unfair to its music service. The Swedish-based music company said that Apple didn't approve a new version of Spotify's iOS app because "it didn't want competition for Apple Music." The Cupertino-based company has responded to the accusations. In a letter sent to Spotify general counsel Horacio Gutierrez on Friday, Apple general counsel Bruce Sewell rebutted the streaming music service's allegations, adding "we find it troubling that you are asking for exemptions to the rules we apply to all developers and are publicly resorting to rumors and half-truths about our service," Sewell wrote. BuzzFeed News reports:"Our guidelines apply equally to all app developers, whether they are game developers, e-book sellers, video-streaming services or digital music distributors; and regardless of whether or not they compete against Apple. We did not alter our behavior or our rules when we introduced our own music streaming service or when Spotify became a competitor," Sewell explains. "Ironically, it is now Spotify that wants things to be different by asking for preferential treatment from Apple." And as for Spotify's suggestion that Apple is treading on dangerous, anticompetitive ground, well, Sewell doesn't seem too concerned. "There is nothing in Apple's conduct that 'amounts to a violation of applicable antitrust laws.' Far from it," Sewell, writes after wryly observing that not only has Apple's platform generated "hundreds of millions of dollars in incremental revenue to Spotify"; but that the Spotify App currently in the App Store is still in violation of Apple's guidelines. "I would be happy to facilitate an expeditious review and approval of your app as soon as you provide us with something that is compliant with the App Store's rules," he quips.Apple commentator John Gruber, writing for DaringFireball:Cry me a river. Spotify has long charged $12.99 via in-app subscriptions to get around the 30 percent "App Store tax". And Apple has now cut the long-term subscription split from 70-30 to 85-15. And Spotify is the streaming service most at war with artists over their abysmal royalty rates. Read between the lines and the real message here is that Apple Music is kicking Spotify's ass.

According to the Wall Street Journal, Apple's upcoming iPhone won't have a 3.5mm headphone jack. The news has already upset many people. The Verge's Nilay Patel wrote on Tuesday that the decision of getting rid of the legacy headphone port is "user hostile and stupid." Apple commentator John Gruber makes a case for why Apple's supposed move is not a bad idea at all. He writes:Patel misses the bigger problem. It's not enforcement of DRM on audio playback. It's enforcement of the MFi Program for certifying hardware that uses the Lightning port. Right now any headphone maker in the world can make any headphones they want for the standard jack. Not so with the Lightning port.He adds that the existing analog headphone jack "is more costly in terms of depth than thickness," and by getting rid of it, Apple could use the extra real estate to stuff in more battery juice. Addressing Patel's point that the move of ditching a deeply established standard will "disproportionately impact accessibility," Gruber adds that "enabling, open, and democratizing" have never been high on Apple's list of priorities for external ports. Gruber also addressed Patel's argument that introducing a Lightning Port-enabled headphone feature will make Android and iPhone headphones incompatible. He wrote: Why would Apple care about headphone compatibility with Android? If Apple gave two shits about port compatibility with Android, iPhones would have Micro-USB ports. In 1998 people used floppy drives extensively for sneaker-netting files between Macs and PCs. That didn't stop Apple from dropping it.As for "nobody is asking" Apple to remove headphone jack from the next iPhone, Gruber reminds: This is how it goes. If it weren't for Apple we'd probably still be using computers with VGA and serial ports. The essence of Apple is that they make design decisions "no one asked for".The 3.5mm headphone jack has been around for decades. We can either live with it forever, or try doing something better instead. History suggests that OEMs from across the world quickly replicate Apple's move. Just the idea of Apple removing the headphone jack -- the rumor of which first began last year -- arguably played an instrumental role in some smartphones shipping without the legacy port this year. If this is a change that we really need, Apple is perhaps the best company to set the tone for it. Though, whether we really need to get rid of the headphone jack remains debatable.

According to the Wall Street Journal, Apple's upcoming iPhone won't have a 3.5mm headphone jack. The news has already upset many people. The Verge's Nilay Patel wrote on Tuesday that the decision of getting rid of the legacy headphone port is "user hostile and stupid." Apple commentator John Gruber makes a case for why Apple's supposed move is not a bad idea at all. He writes:Patel misses the bigger problem. It's not enforcement of DRM on audio playback. It's enforcement of the MFi Program for certifying hardware that uses the Lightning port. Right now any headphone maker in the world can make any headphones they want for the standard jack. Not so with the Lightning port.He adds that the existing analog headphone jack "is more costly in terms of depth than thickness," and by getting rid of it, Apple could use the extra real estate to stuff in more battery juice. Addressing Patel's point that the move of ditching a deeply established standard will "disproportionately impact accessibility," Gruber adds that "enabling, open, and democratizing" have never been high on Apple's list of priorities for external ports. Gruber also addressed Patel's argument that introducing a Lightning Port-enabled headphone feature will make Android and iPhone headphones incompatible. He wrote: Why would Apple care about headphone compatibility with Android? If Apple gave two shits about port compatibility with Android, iPhones would have Micro-USB ports. In 1998 people used floppy drives extensively for sneaker-netting files between Macs and PCs. That didn't stop Apple from dropping it.As for "nobody is asking" Apple to remove headphone jack from the next iPhone, Gruber reminds: This is how it goes. If it weren't for Apple we'd probably still be using computers with VGA and serial ports. The essence of Apple is that they make design decisions "no one asked for".The 3.5mm headphone jack has been around for decades. We can either live with it forever, or try doing something better instead. History suggests that OEMs from across the world quickly replicate Apple's move. Just the idea of Apple removing the headphone jack -- the rumor of which first began last year -- arguably played an instrumental role in some smartphones shipping without the legacy port this year. If this is a change that we really need, Apple is perhaps the best company to set the tone for it. Though, whether we really need to get rid of the headphone jack remains debatable.

Apple says it will now take a smaller cut of commission from app developers provided they have customers who stick with their subscription model for longer than a year. Phil Schiller, Apple's Senior Vice President of Worldwide Marketing, told The Verge in an interview that the company will revise the 70-30 split for such developers to 85-15. In addition, the company will also begin showing search ads for apps in its iOS App Store search results. Also, the company says it is speeding up app review times "to the point where 50 percent of submitted apps are now reviewed in 24 hours, and 90 percent are reviewed within 48 hours." From the report: If the new subscription model becomes widely adopted, it will represent a fundamental shift in the economics of the App Store. Developers will be incentivized to sell their apps for a recurring fee instead of a one-time cost. It could change the way consumers pay for certain apps, but it also presents a massive opportunity for developers, many of whom feel the app economy has been become moribund in recent years. And as iPhone sales growth slows, a move to app subscriptions is another way for Apple wring more profits from its existing user base.Apple columnist John Gruber has more details.

Apple is considering big changes to the App Store, according to a Bloomberg report. The publication claims that the iPhone maker has a team working on "paid searches" -- something similar to Google's model. Under this, the company will charge its developers for showing their apps among top search results. Apple critic John Gruber writes: This sounds like a terrible idea. The one and only thing Apple should do with App Store search is make it more accurate. They don't need to squeeze any more money from it. More accurate, reliable App Store search would help users and help good developers. It's downright embarrassing that App Store search is still so bad. Google web search is better for searching Apple's App Store than the App Store's built-in search. That's the problem Apple needs to address.

An anonymous reader writes: The Apple Watch's release date has arrived: retailers around the world have quietly begun putting them on their shelves, and customers are beginning to receive their shipments. Reviews have been out for a while, including thoughtful ones from John Gruber and Nilay Patel. Apple has published a full user guide for the software, and iFixit has put up a full teardown to take a look at the hardware. They give it a repairability score of 5 out of 10, saying that the screen and battery are easily replaced, but not much else is. Though Apple designated the watch "water-resistant" rather than "waterproof", early tests show it's able to withstand a shower and a swim in the pool without failing. Ars has an article about the difficulty of making games for the Apple Watch, and Wired has a piece detailing its creation.

BartlebyScrivener writes "I am a author, screenwriter, law prof, and a hobbyist programmer. I love MacVim and write almost everything in it: Exams, novels, even screenplays now that Fountain is available. I use LaTeX and WordPress and so on, but several years ago I discovered Markdown and the wonderful Pandoc. I searched Slashdot expecting to find lively discussions of both Markdown and Pandoc, but found nothing. Do Slashdotters look down their noses at these tools and do their work in HTML and LaTeX? I can't imagine computer geeks using Word instead of their favorite text editors. If not Markdown and Pandoc, what tools do Slashdotters use when they create documents that probably need to be distributed in more than one format: HTML, PDF, EPUB or perhaps even docx?" And then there's DocBook, LyX, and a host of other markup languages. What do you use, in what context?

Nerval's Lobster writes "Why did Apple hire former Adobe CTO Kevin Lynch as vice president of technology? Adobe and Apple spent years fighting a much-publicized battle over the latter's decision to ban Adobe Flash from iOS devices. Former Apple CEO Steve Jobs was very public in his condemnation of Flash as a tool for rich-content playback, denigrating it in an April 2010 letter posted on Apple's Website as flawed with regard to battery life, security, reliability and performance. Lynch was very much the public face of Adobe's public-relations pushback to Apple's criticism; in a corporate video shot for an Adobe developer conference in 2009, he even helped run an iPhone over with a steamroller. (Hat tip to Daring Fireball's John Gruber for digging that video up.) As recently as 2010, he was still arguing that Flash was superior to HTML5, which eventually surpassed it to become the virtual industry standard for Web-based rich content. It's interesting to speculate whether Steve Jobs would have hired someone who so publicly denigrated Apple's flagship product. But Jobs is dead, and his corporate successors in Cupertino—tasked with leading Apple through a period of fierce competition — obviously looked at Lynch and decided he'd make a perfect fit as an executive."

As Microsoft prepares for the launch of Windows Phone 8 devices, its most important push into the smartphone industry to date, speculation is rampant about whether or not consumers will continue to ignore Windows-based phones. There are many obvious ways Microsoft could misstep and lose its chance to participate in another generation of phones, but what would it take for Windows Phone 8 to succeed? To start, they can take advantage of manufacturers who are worried about being pursued over patent claims. They could also work to establish the permanence of Windows Phone 8, after the upgrade inflexibility involved with Windows Phone 7 and Windows Mobile 6.5. Finally, they could take a page out of Amazon's book and make WP8 devices more about services.