Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't get why Apple insists on locking down new products and features. Let developers take advantage of them now, it'll be opened up eventually anyway.

That's the way Apple does things. Slowly slowly catchy monkey. Start small and add extra functionality with each new version so we keep upgrading.

----------

Would people be too lazy to pull their phone out of their pockets and use that?

In a word yes. Why get your phone out of your pocket, log in then find the right app when a quick glance at your wrist followed by a few taps does the trick. Lazy maybe but very handy all the same.
 
That's the way Apple does things. Slowly slowly catchy monkey. Start small and add extra functionality with each new version so we keep upgrading.

I don't think going slow with this SDK is about obsolescence. This is a brand new product where use case/usage patterns is still a big unknown. Plus the rumors suggest Apple is still having battery issues. It only makes sense to start slow. Plus it could simply be the case that the SDK for native apps just isn't ready yet. Perhaps it will be announced at WWDC.
 
i just feel like wearables will become so powerful they'll replace many people's phones altogether. not yours or mine, maybe, but in 5 years the apple watch will be about as powerful as the i6 is today.

The main limitation is battery. If Battery density was up to snuff, 5 years would be conservative. Right now, the watch has about the same processor as the A5, that's only 3 years behind the current Iphone!!

Actually putting a super-powerful processor in a watch, especially one that works at a low clock speed is very advantageous. Since, you want the processor to sleep most of the time.

From what I see, in the watch, eventually it won't be the processor that will be the limitation, but the screen and network equipment. If you could have high refresh, high resolution color screens that function on next to no battery, it would be a huge boon.
 
Which are the future. Safari in iOS 8 has WebGL enabled - as soon as developers start to realize that and take advantage of it, native apps will die swiftly (pun intended.)

I know most responded to disagree, but you, sir, are 100% correct

Web apps are the future, many smaller apps have been replaced by links as their web version is now better than app version. Web apps are universal, scalable, and save a lot of development cost. Devices are becoming more powerful too and can handle them

Cloud apps are taking over even in enterprise world; just ask Oracle how Salesforce.com stole their lunch
 
Which entirely misses the point of the smart watch.

Yes, all that functionality exists on the phone already. Heck, I believe OnStar's phone app lets me remote start and lock/unlock my car remote already (if I ever set it up), but doing that on my phone is actually more of a hassle than using the key/remote my car came with. I have to pull my phone out of my pocket, unlock it, launch an app, and hit whichever commands do what I want them to do. Compare that to the remote: I tap the Lock button, tap the Remote Start button, then tap the Unlock button, and I'm set ... and I can do all of that without pulling my hand out of my pocket to look at the remote.

The Apple Watch would potentially be closer to the remote than it would be to the phone: raise my arm, select the app, and tap whatever I need to do. Bam.

It's not laziness, it's convenience. It creates fewer actions necessary to accomplish the same task, particularly because the Watch is on my arm and the apps are designed specifically to be easy to use. Brief interactions, then done. Least resistance.

That's why this is so compelling, and why I think this will be a huge hit. It will be the path of least resistance to so many actions during our day, so many little things that become just automatic reflexes, and I fully believe Mr. Cook when he says he can't live without it.

im with you there and im pretty sure if i had a tesla my first glance app will be that :D your keys and your wallet on your wrist. lucky US. :(
 
Would people be too lazy to pull their phone out of their pockets and use that?

Most of my pants have frayed pockets due to my phone. Not to lazy to pull it out, but for little things like texts, stock prices, calendar, etc., a glance at my wrist makes more sense. Removing my phone and unlocking it vs. turning my wrist, makes the watch worth it for me.
 
I know most responded to disagree, but you, sir, are 100% correct

Web apps are the future, many smaller apps have been replaced by links as their web version is now better than app version. Web apps are universal, scalable, and save a lot of development cost. Devices are becoming more powerful too and can handle them

Cloud apps are taking over even in enterprise world; just ask Oracle how Salesforce.com stole their lunch

You want a minimal footprint on such an embedded and limited form factor product. That means traditional apps, focused and optimized with energy efficiency in mind. Not WebGL, nor Javascript Apps.

----------

You think that there is something ridiculous about spending $350 on a watch when you spent $650+ on a phone? Oy vay!

----------



Can't believe anyone wearing a Rolex would be concerned about the aesthetics of their watch. Butt ugliest timepiece ever made.

No, but you'll be spending, baseline, $1000 to work together.
 
Agreed...If the simple iOS apps were web apps the iPhone could be so much cooler. I'm not this ultra die hard, blindly accept anything Jobs said, type of person; but he was right to try and limit the iPhone to web apps...unfortunately the bandwidth just wasn't (and probably still isn't) there. :apple:

----------



The question of hour is: will gen1 support the second SDK?

How is that the question of the hour? The article clearly states the second SKD is coming with the watch release
 
You bring up an excellent point, which as far as I'm aware Apple has kept quiet on, and it will be interesting if they explain this at their pre-launch gathering most are expecting to see.

Or if they carefully decide to deliberately not mention it.

What am I talking about?
The maximum distance the Watch can be from the iPhone and still function.

In your scenario, and for everyone else, in home life, this is a major, and I mean MAJOR point that will make a vast difference to how the watch functions for you day to day.

If the iPhone just had to be in the house somewhere, or downstairs where you are, or in the same room as you, or within a few feet of you.

That fundamentally changes how the watch will feel and work for many.

If for example the iPhone just had to be in the home/apartment somewhere, then the watch will be great, and you can just relax when wearing it at home.

If it however had to be within say 10 feet, then it's a mostly dead device whilst you are at home going about your day to day business.

Given how much of a difference in use and function this will make the watch I would hope Apple will explain this reliable distance it can be from the iPhone fully before launch

Yeah good point - I'm not sure if it has wifi or just bluetooth? We could work out the distance based on this really.
 
I know most responded to disagree, but you, sir, are 100% correct

Web apps are the future, many smaller apps have been replaced by links as their web version is now better than app version. Web apps are universal, scalable, and save a lot of development cost. Devices are becoming more powerful too and can handle them

Cloud apps are taking over even in enterprise world; just ask Oracle how Salesforce.com stole their lunch

Also, if you check out Nintendo's developer page, they tell you to either use Unity, or to make your game in HTML5/WebGL/asm.js (and the former has the later as a possible build target).
 
I don't think going slow with this SDK is about obsolescence. This is a brand new product where use case/usage patterns is still a big unknown. Plus the rumors suggest Apple is still having battery issues. It only makes sense to start slow. Plus it could simply be the case that the SDK for native apps just isn't ready yet. Perhaps it will be announced at WWDC.
I can see this living or dying on the battery life. It's one thing to charge your iPhone part way through the day but I wouldn't want to have to do that with a watch. The battery has to last from breakfast to bed time which means at least 16 hours.
 
Yeah good point - I'm not sure if it has wifi or just bluetooth? We could work out the distance based on this really.

My own conjecture is that the Apple Watch is using a custom network protocol (likely a modified version of either Wi-Fi or Bluetooth), at least for 3rd party apps that rely on the iPhone to run. I am thinking that it's akin to the Nintendo Wii U GamePad, which decodes H.264 video that's actually generated on the Wii U system as opposed to on the GamePad itself. Such a setup would allow the Apple Watch to offload the CPU- and GPU-intensive tasks (aka battery-consuming operations) to the iPhone as the Apple Watch then only has to decompress video and handle some basic touch gestures. The Wii U GamePad has very low latency in my opinion--you can play games entirely from the GamePad rather than on a TV--so Apple Watch apps should conceivably have a fast and responsive UI despite technically running on the iPhone.

Regarding range, the recommendation is 24 to 27.5 feet for the Wii U GamePad, but some people have seen up to 40 to 60 feet (http://www.ign.com/wikis/wii-u/Increase_Wii_U_and_Gamepad_Range). While the Apple Watch hardware is surely different, I would be surprised to see that wide of a range. The range also likely varies greatly depending on the environment, indoors versus outdoors and open space versus lots of walls and floors.
 
has anyone noticed that it said 300 miles range and still had 11% remaining of charge left. Is this a hint to a better tesla?
 
The main limitation is battery. If Battery density was up to snuff, 5 years would be conservative. Right now, the watch has about the same processor as the A5, that's only 3 years behind the current Iphone!!

Actually putting a super-powerful processor in a watch, especially one that works at a low clock speed is very advantageous. Since, you want the processor to sleep most of the time.

From what I see, in the watch, eventually it won't be the processor that will be the limitation, but the screen and network equipment. If you could have high refresh, high resolution color screens that function on next to no battery, it would be a huge boon.

I'm thinking that supercapacitors are the thing. Charge in 30-90 seconds, last all day or longer. Heck, I wouldn't be surprised to see the chargers in bathroom stalls. :eek:

----------

Would people be too lazy to pull their phone out of their pockets and use that?

Yep... The whole idea of having a timepiece on your wrist, instead of going to the town square to know the time is completely ludicrous.

Next thing you know, people will get rid of their horses (wait! That's for lazy non-walkers) and use those newfangled horseless carriages to go to town.

It's all been downhill since the wheel, lever, and the inclined plane.
 
I have never seen an Apple product in recent history attract so many people who want to express how much they aren't going to buy the product. Every thread coming out of the front page - irrespective of the subject of the front page article there seems to be a need to come out and state how much you don't want to buy this thing.

I personally don't want to buy a Toyota but I don't post incessantly on Toyota forums about how much I don't want one.

It is astonishing.

It is also amazaing how if someone describes a use case for the watch then people have to deride that use case.

I am looking forward to this and how it develops over the next few years. Much like my iPads and iPhones there will be a trickle down to family as it gets updated. I fully expect to update annually in the first three years and then move to a two-three year cycle - much like I have with the iPad.

One of the great things will be shutting off notifications on the ipad and iPhone - great when giving a presentation to your boss and you get interrupted by notifications of emails from recruiters... Also notifications wont be appearing whilst I am playing a game or watching a movie.

And the best thing is that for people who don't want it - they actually wont be forced to buy it.

----------

has anyone noticed that it said 300 miles range and still had 11% remaining of charge left. Is this a hint to a better tesla?

I think it was 89% charged - which ties back to the 500M range on a full charge roughly?
 
i just feel like wearables will become so powerful they'll replace many people's phones altogether. not yours or mine, maybe, but in 5 years the apple watch will be about as powerful as the i6 is today.

I have a hard time with the :apple:Watch as a standalone device replacing the iPhone. With the iPhone 6/6+, people are looking for larger screens to do stuff, and the :apple:Watch has its purpose, a smartphone replacement doesn't seem to be in the cards.

I am willing to be wrong on this one, but I think we'll need a paradigm shift to holographic displays, and better input media. It's bad enough to type on an iPhone (vs. a computer), and I don't think the watch will fill that gap.
 
We currently have a Ford Fiesta with keyless entry. It senses the key is close and allows you to just walk up, pruss a little button on the door handle while pulling it open, and unlock the car. Once you get in, hit push to start, you are set to go.

If we get something like this implemented safely I would actually buy an Apple watch. These keys alone cost $300. I would happily just buy a watch for that and call it a day. Remote start is even a plus.

Unfortunately I am sure the car companies will add some sort of "programming fee" or something to the mix if/when this becomes a reality.

I don't see this being the norm for some years, though. And realistically this could be achieved with a phone too (which I would actually prefer).
 
I can see this living or dying on the battery life. It's one thing to charge your iPhone part way through the day but I wouldn't want to have to do that with a watch. The battery has to last from breakfast to bed time which means at least 16 hours.

IT DEPENDS WHAT YOU DO. Seriously!! Can your phone last 16h if your playing a decent game on it? Not at all.

The phone needs to cover all the average usage of 90% of people to be successful.
 
I have said this a number of times.

I honestly think the main reaon why Apple are restricting things in this way has more to do with battery life than anything else.

They know full well that battery life "is" the BIGGEST NEGATIVE of these type of devices right now, especially when the general public are used to, and have been used to watches lasting a couple of years or more on a single tiny replaceable battery.

Going from devices that lasted years without worrying about them to device that may only last hours, or a day with very light use is one hell of a change.

Deliberately limiting what devs can do with the watch, and not allowing, what one may call full, feature rich apps that customers would probably spend too long using/enjoying, and hence using up battery life.
Is Apples deliberate attempt at trying to make the battery life seem to appear better than it really is.

They are doing all they can to limit what the watch can be used for right now, to stop people buying this new device, playing with it all the time, and then the Internet reviews/chat and printed media (magazines, papers) be totally awash with unhappy critical user reports of the battery only lasting a few hours.

That's the real reason I think they are limiting this so harshly, to avoid early mass negative publicity and harming sales too much as people who are currently thinking about buying one decide they will wait for a later model that's better.

I agree but why even make the watch so sophisticated in the first place. It's like bragging about a car that can go 200 MPH but the speed limiter is pegged at 65 just to save gas.
 
I agree but why even make the watch so sophisticated in the first place. It's like bragging about a car that can go 200 MPH but the speed limiter is pegged at 65 just to save gas.

Because, just like with the iPhone - once people start using it, they will mind less as functionality increases.

Bad analogy alert: The written experiment of throwing a frog in a hot pot of water and it jumping out. You put it in and slowly start raising the temperature - it's not going to go anywhere.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.