Apple Tests iPhone 6? Not A Shocker
By Eric Zeman
InformationWeek
Well, duh.
Apple releases a new iPhone and a new version of iOS every year. These things don't pop up overnight, you know. Apple designer Jony Ive doesn't walk across the water and accept the new i-device from Lady of the Lake. The iPhone takes time to design, engineer and test. In fact, there's an industry term for it: It's called "research and development."
New smartphones often take between 12 and 18 months to move from blueprint to retail. Apple is likely already working on the iPhone 7 and iPhone 8. In fact, it probably has two to four new iPhones in various stages of development. This is a phenomenon called a "roadmap." You know, a plan that spans several years so the company knows where it is headed. It's a handy thing to have around.
[ Not every smartphone is a beauty like Apple's iPhone. Check out the 5 Ugliest Smartphones Of 2012. ]
So what do the server logs tell us right now?
Apple uses a slightly different code to reference its i-devices. For example, we call the latest iPhone the iPhone 5, but Apple refers to it as the iPhone5,1 or iPhone 5,2 depending on the variant. The iPhone 4S was the iPhone4,1, and the iPhone 4 was the iPhone 3,1. These device names (think of them as chassis designators) are what shows up in code when the associated device is used to surf the Web. The same goes for iPads. Server logs unintentionally revealed this internal naming scheme years ago.
The "iPhone6,1" is the new device popping up. This means that there are early builds of the next-generation iPhone being used by Apple's engineers for testing. One of their tests is to surf the Web, hence the server logs. The designation tells us that Apple has a new piece of hardware on deck, but that's all. It doesn't provide any details about the design, features or anything else.
We could have guessed as much without the server logs, based on Apple's past behavior of yearly hardware and software upgrades.
Though there's a rough correlation between the designator and the final name of the i-device products, it is not set in stone. If Apple sticks with its actual product naming scheme, the iPhone6,1 might actually be the iPhone 5S (remember, there was an iPhone 3G and iPhone 3GS; followed by the iPhone 4 and iPhone 4S).
At the end of the day, we have to assume that Apple (and every other company, for that matter) is always working on new products.
Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).
Tech spending is looking up, but IT must focus more on customers and less on internal systems. Also in the new, all-digital Outlook 2013 issue of InformationWeek: Five painless rules for encryption. (Free registration required.)
 |
To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Subscribe to RSSInformationWeek Reports
Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.
Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.
Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.
The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.