Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I get 227. Plug in the following inputs:
Horizontal: 272
Vertical: 340
Diagonal: 1.915" [(38mm^2+30.4mm^2)^.5]/25.4

The math is the old pythagorean theorem (a squared + b squared = c squared). The conversion ratio of mm to inches is 25.4:1.

Or an easier way = 340/38*25.4.

Either way, you get to 227 ppi. By comparison, the iPad Air 2 is 264 ppi.


You're probably close but I'm quite sure Pythagoras only works on a 3-4-5 triangle
 
AppleTV/Mac Mini - I think these product lines will be eliminated or severely cut back in effort to promote an integrated device using the best of both devices.

Not that line of thinking again. :mad:

Just because a very vocal handful of Mac mini owners use their Mac mini as a HTPC doesn't mean Apple should somehow merge the Mac mini with the Apple TV. It would increase the price of the Apple TV (which needs to go down in price to compete with the alternatives) and it would lower the usefulness of the Mac mini (which is the only screen-less option for most people since the Mac Pro is not priced for regular users).

Hey, let's drop the MacBook Air! After all, MacBook Air users could buy an iPad with a keyboard, right? :rolleyes:
 
It's still more then my second phone. Sony W810i with 176 x 220 resolution.
 
I suspect that the leading "killer app" for this (aside from fitness) will be Apple Pay - because sometimes lifting your phone is too much work. Especially those that upgrades from a 4" phone...

Doubt it.

ApplePay uses TouchID, so you would still need to grab your phone.

I suspect that the reason Apple have focused so heavily on the fashion aspect of the Apple watch is because they have no killer app.

My opinion is that they're hoping people will buy it for the watch itself (fashion statement), with the added bonus of notifications etc., and hoping that some developer finds some useful way to use the technology before later versions of the watch are released.

I also suspect that the phone will eventually be marketed like the galaxy gear/note3 - to compliment the 6+. It's a big phone to carry around, sometimes you want access to the most basic features without having to get it out of your bag.

But those are just my thoughts.
 
The documentation is in points but this article mentions it in pixels.
The 2 are not interchangeable.

The actual resolutions of the devices will be 544x680 and 624x780. These are retina screens with retina assets, so even though the functional resolution is lower, the actual resolutions is double what the article says.


So you could fit more than two copies of the entire display of the original Mac (512×342) on one of these things?
Or more than eight copies (on the large version) of the original Apple ][ display (280×192)?!
I find that impressive in some weird, useless way.
I still think this thing is going to be a huge flop. But a remarkably elegant and technically very impressive flop.

----------

You're probably close but I'm quite sure Pythagoras only works on a 3-4-5 triangle

You probably should not be quite so sure of that.
http://en.wikipedia.org/wiki/Pythagorean_theorem
 
Last edited:
I don't know if it's likely, but it would be very bold for Apple to charge the same price the two sizes.

I see all sorts of people make their choice of phone size based on the price. Wouldn't it be cool if Apple's sales force could help people decide on what size watch to get based solely on how it looks on their arm and nothing else?

These are supposed to be fashion pieces, after all. Does Apple want to see ludicrously tiny watches on large men's arms because they wanted to save a few bucks? That doesn't help Apple sell more watches.

Yes, I know the bigger watch uses more materials, but it's nowhere close to the difference between an iPad Air and Mini. And it's not like the markup on these things isn't high enough to cover the few extra cents in glass per larger watch.

I dunno, it would certainly be a departure from every other Apple product. But in this one case I could see it being beneficial to Apple.

Then we would see the ones with the small wrist buying the larger watch, thinking the larger is better :)
But honestly, I don't think Apple should charge the same for both if the cost of making them is different. The difference could be small enough so people don't need to make their buying decision based on the price. Like $20 or 30 more? I wouldn't buy a watch that look small on my wrist just because it cost $30 less! While I already managed to splash a thousand $ or more on both, Apple watch and iPhone.
 
You're probably close but I'm quite sure Pythagoras only works on a 3-4-5 triangle

I'm quite sure you're wrong about that. The Pythagorean theorem is easily proven for all right triangles (in Euclidean space, that is).

http://en.wikipedia.org/wiki/Pythagorean_theorem

The sequence 345 is a pythagorean triple -- 3 integers that form a right triangle. This is handy for constructing proper right angles in the real world.

http://en.wikipedia.org/wiki/Pythagorean_triple
 
I'd suggest also a model for dwarfs one for elves and one for nazgul.
Obviously with different sizes... :D
 
Overall first impressions:

1) They are taking a "second screen" strategy to the Apple Watch. There is no concept of a stand alone watch app. This is a big break for both Pebble and Google Wear.

2) The Xcode interface was a bit clunky. Took a bit to figure out how to show the watch screen in the simulator.

3) There should be a feature to simulate an Apple Watch on an iOS device that is provisioned for development. Thus, you have your iOS app run on one iOS device and another iOS device showing the Apple Watch views. An iPod Touch is excellent for this.

4) Apple Watch "apps" are just an extension of an iPhone app. Thus, to use Apple Watch "apps" you need an iPhone. No third party connectivity to Android nor Windows smart phones.

5) There is a proprietary wireless link (probably BLE without the throttling) between iPhone and Apple Watch to get apps on the watch using the WatchKit extensions.

6) The narrative voice in the half hour tutorial was really annoying. It is probably a product manager that won or lost the office draw. If they can afford to keep a staffed sound studio in the loop, they can afford a good voice actor.

7) This avoids a new product type in the App Store. It is just an "Apple Watch Enabled" category in the store.

8) It was probably targeted for this Christmas season but due to the Sapphire Crystal Greek Tragedy, it is delayed 'til 1Q15.

9) Dozens of millionaires to be made from the new generation of "fart apps." If you are coding now, don't look for the best, just look the fun and stupid.

10) If someone can spend $4000 for a gold Edition Apple Watch, you can charge $100 for a high end app. Go for it.

11) While there is money in making apps. There is a HUGE market for custom, third party Apple Watch wristbands.
 
Last edited:
I get 227. Remember, you need to input the diagonal length of the screen. For the 38mm version, it is 1.915" [38mm^2+30.4mm^2)^0.5]/25.4 = 1.915

Granted, this is low-end because I didn't factor in the bezel, but I think somewhere around 250-270 is plausible.

The bezel makes a big difference in the PPI

Bigger one 390*312 = 121680 pixels
Smaller one. 340*272 = 92480

(a 2.5 mm bezel gives, counting rounding)
Bigger one : 1.7 square inch (37*29.6 = 1767) / (25.4*25.4) , so we have 121680 / 1.7 = (268 ppi) squared
Smaller one: 1.34 square inch (33mm x 26.2mm = 864.6 ) / (25.4*25.4) , So we have 92480 / 1.34 = (263 ppi)squared
So, around 265 ppi

(With a 4mm bezel, counting rounding)
Bigger one : 1.43 (34 * 27.2) / (25.4*25.4) , so we have 121680 / 1.27 = (291 ppi) squared
Smaller one : 1.116 (30 * 24 ) / (25.4 * 25.4) , so we have 92480/1.27= (288ppi) squared

So, 265-290 ppi

My feeling is the bezel is more than 2.5 mm on both side, so my gut is saying that the watch has :

280 PPI for both sizes.

----------

Overall first impressions:

1) They are taking a "second screen" strategy to the Apple Watch. There is no concept of a stand alone watch app. This is a big break for both Pebble and Google Wear.

2) The Xcode interface was a bit clunky. Took a bit to figure out how to show the watch screen in the simulator.

3) There should be a feature to simulate an Apple Watch on an iOS device that is provisioned for development. Thus, you have your iOS app run on one iOS device and another iOS device showing the Apple Watch views. An iPod Touch is excellent for this.

4) Apple Watch "apps" are just an extension of an iPhone app. Thus, to use Apple Watch "apps" you need an iPhone. No third party connectivity to Android nor Windows smart phones.

5) There is a proprietary wireless link (probably BLE without the throttling) between iPhone and Apple Watch to get apps on the watch using the WatchKit extensions.

6) The narrative voice in the half hour tutorial was really annoying. It is probably a product manager that won or lost the office draw. If they can afford to keep a staffed sound studio in the loop, they can afford a good voice actor.

7) This avoids a new product type in the App Store. It is just an "Apple Watch Enabled" category in the store.

8) It was probably targeted for this Christmas season but due to the Sapphire Crystal Greek Tragedy, it is delayed 'til 1Q15.

9) Dozens of millionaires to be made from the new generation of "fart apps." If you are coding now, don't look for the best, just look the fun and stupid.

10) If someone can spend $4000 for a gold Edition Apple Watch, you can charge $100 for a high end app. Go for it.

11) While there is money in making apps. There is a HUGE market for custom, third party Apple Watch wristbands.

I think will do as always. Be very tight about what goes on the watch, and how people are using watch resources, at first, then they will open it up once they're sure all is going fine on the watch. That way people don't blame Apple if apps mess up their watch.
 
(I'm also very curious if the larger one will actually cost more to make or the difficulties in making things even smaller will matter).

There will be a slight materials and manufacturing cost difference. The larger screen may be a little more expensive. The internals are likely to be the same. Any additional development cost will be completely swamped by the volume of sales. So the answer is probably "not really". You can, after all, buy a fully working traditional watch for a few pounds/dollars.
 
Overall first impressions:

1) They are taking a "second screen" strategy to the Apple Watch. There is no concept of a stand alone watch app. This is a big break for both Pebble and Google Wear.

I thought native apps were coming in 2015 (probably announced at WWDC)?

http://www.apple.com/pr/library/2014/11/18Developers-Start-Designing-Apps-for-Apple-Watch.html

The iOS 8.2 SDK beta including WatchKit is available immediately for iOS Developer Program members at developer.apple.com/watchkit. The WatchKit site includes programming guides, human interface guidelines, templates and more. Starting later next year, developers will be able to create fully native apps for Apple Watch.


----------

Doubt it.

ApplePay uses TouchID, so you would still need to grab your phone.

https://www.macrumors.com/2014/09/10/apple-watch-apple-pay-security/

Both Rene Ritchie of iMore and Cult of Mac report that when a user first puts on the Watch they must type in a PIN code to authorize Apple Pay. Once it's on, the Watch uses constant skin contact, which it can sense using the four sapphire-covered lenses on the underside of the device, to authorize payments. However, once the device is removed from a user's wrist, they must re-enter their PIN when putting the device back on their wrist.

Thanks to sensors on the Apple Watch’s back, the device can tell when it’s being worn and when it has been taken off. When you first put the watch on, you must enter a code. When the watch is removed from your wrist, the watch locks itself and can’t be used for payments unless the code is entered again.

MasterCard's mobile payment executive Ed McLaughlin also told Re/code that the Watch would use the four sensors on the back of the device as a security measure, while Visa CEO Charlie Scharf said that Apple understood the risks of contactless payments and has a solution.
 
Not that line of thinking again. :mad:

Just because a very vocal handful of Mac mini owners use their Mac mini as a HTPC doesn't mean Apple should somehow merge the Mac mini with the Apple TV. It would increase the price of the Apple TV (which needs to go down in price to compete with the alternatives) and it would lower the usefulness of the Mac mini (which is the only screen-less option for most people since the Mac Pro is not priced for regular users).

Hey, let's drop the MacBook Air! After all, MacBook Air users could buy an iPad with a keyboard, right? :rolleyes:

If the 2014 Mac Mini is any indication, they are starting to trim back on the features and specs. The next Mac Mini refresh might be even more limited than the 2014 one. Hey I use my mac mini as a desktop machine and I love it.
 
A rotary encoder by any other name...

$100 bucks says Ive wrote this poetic malarkey...

What kills me is that the "digital crown" is really just a rotary encoder with a push button. FYI Apple, you didn't invent the rotary encoder, they've been around for a long time and have found their way into lots and lots of products before the Apple Watch. I found this patent from '86 for an optical rotary encoder, so a magnetic encoder might even be older than that. https://www.google.com/patents/WO1987006338A1?cl=en&dq=rotary+encoder&hl=en&sa=X&ei=xKRsVMmuMtfXoASQsIKoDA&ved=0CCMQ6AEwATgK
 
Last edited:
What kills me is that the "digital crown" is really just a rotary encoder with a push button. FYI Apple, you didn't invent the rotary encoder, they've been around for a long time and have found their way into lots and lots of products before the Apple Watch. I found this patent from '86 for an optical rotary encoder, so a magnetic encoder might even be older than that. https://www.google.com/patents/WO1987006338A1?cl=en&dq=rotary+encoder&hl=en&sa=X&ei=xKRsVMmuMtfXoASQsIKoDA&ved=0CCMQ6AEwATgK

A lot of people already use a "digital crown". It's called a mouse scrollwheel. But just like Apple calls their HiDPI displays "retina", they're calling their rotary encoder "digital crown". It's marketing.
 
A lot of people already use a "digital crown". It's called a mouse scrollwheel. But just like Apple calls their HiDPI displays "retina", they're calling their rotary encoder "digital crown". It's marketing.

actually on an ordinary watch it's already called a crown, but because this one doesn't physically turn the hour and minute hands of the watch and instead sends digital information to do that, plus more they call it the "digital crown". Makes perfect sense to me and everyone understands that.

most of the worlds population have no idea what a rotary encoder is - even if that is the technology being used to convert the analogue rotations to digital information and yes it looks like the scroll wheel of a mouse works in a similar fashion.
 
Last edited:
A lot of people already use a "digital crown". It's called a mouse scrollwheel. But just like Apple calls their HiDPI displays "retina", they're calling their rotary encoder "digital crown". It's marketing.

Wait a minute.

Are you actually suggesting this feature on the Apple Watch should be called the "mouse scrollwheel"?

Even if you're trying to take all marketing out of the naming equation, that is a hilariously out of date and inaccurate descriptor.
 
What kills me is that the "digital crown" is really just a rotary encoder with a push button. FYI Apple, you didn't invent the rotary encoder, they've been around for a long time and have found their way into lots and lots of products before the Apple Watch. I found this patent from '86 for an optical rotary encoder, so a magnetic encoder might even be older than that. https://www.google.com/patents/WO1987006338A1?cl=en&dq=rotary+encoder&hl=en&sa=X&ei=xKRsVMmuMtfXoASQsIKoDA&ved=0CCMQ6AEwATgK

Its already called a crown. So, digital is just to distinguish from the one normally on a watch. In fact, its probably Apple at its most respectful of watch history and the English language...
 
Are you sure about that. Because from where I'm sitting, Apple seems to be marketing the watch as a way to use Apple Pay.

http://www.apple.com/watch/features/ (scroll down.... a lot)

You will have to enter a 4 digit code to use Apple pay on the watch, if the watch does not lose skin contact after this, then you don't have to enter the 4 digit code. If you take the watch off, you have to enter the code again.
 
You will have to enter a 4 digit code to use Apple pay on the watch, if the watch does not lose skin contact after this, then you don't have to enter the 4 digit code. If you take the watch off, you have to enter the code again.

And your point is what? I never said otherwise.
 
do you have any proof of that? or is it just a wild guess from your part? I'm assuming you don't know him, have never met him, nor have ever been in the same room together. just a wild guess on my part tho.

Do you always know the people you criticize personally?

----------

It's not.
And he's still right.

Glassed Silver:mac

People don't tend to use fragmentation to mean broken into two lines. Compare with Android where it's dozens or hundreds.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.