Unofficial iPad 2 Mockup Seen in the Wild at CES

Discussion in 'Apple iPad News' started by Maura, Jan 5, 2011.

By Maura on Jan 5, 2011 at 11:55 AM
  1. Maura

    Expand Collapse
    iPadForums News Team

    Jun 7, 2010
    Thanks Received:

    Engadget reports from CES today that an unofficial mockup of an iPad 2 has been spotted there, cunningly hiding inside an iPad 2 case. The very interesting, and probably-soon-to-be-whisked-away-by-Apple, case comes courtesy of an exhibitor called Dexim, and features a Bluetooth keyboard that is attached magnetically to the front of the cover. Apparently when Engadget asked to put their iPad inside the cover, thinking it was for the current version, the exhibitor told them that it wouldn’t fit as the case was specifically designed for an iPad 2. It would appear from Engadget’s hands-on experience with the case and the aluminium mockup of the iPad 2 inside, that the next-gen iPad will be exactly as those recent case leaks from China have led us to believe – slightly slimmer than the current iPad, with tapered edges similar to that of the current iPod touch, a larger speaker, and the home button closer to the bottom of the iPad. Of course nothing’s actually written in stone until Apple writes it in stone, but it’s certainly strange that so many cases are turning up now with the exact same cut-outs.

    Source: iPad 2 case shows up at CES, packing a mockup iPad 2 -- Engadget


Discussion in 'Apple iPad News' started by Maura, Jan 5, 2011.

    1. jordexj
      You know Engadget has some sort of inside connection with Apple. Apple is always "accidentally" leaking information or accidentally "forgetting" phones in bars where an Engadge rep is conveniently located... This is just genious marketing and Engadget is the Marketing firm doing the soft campaign.
    2. iVan
      I really don't think a second gen mockup would get Apple secrecy police prone to confiscation. They are more active with a first gen device. The worst they'd do now is to take this manufacturer off their privileged developer inside list or fine them...

Share This Page