3/6 Apple iPhone announcements
3/6 Apple iPhone announcements
Exchange ActiveSync licensed from M$, push mail, push contacts, Global address list, Cisco IPsec VPN client, certificates/identities, WPA2/802.1x, enforced security policies, device configuration, remote wipe.
Not terrbily meaningful for individuals and consumers, but this is huge news for the iPhone market potential and what that means to Apple's bottom line.
Not terrbily meaningful for individuals and consumers, but this is huge news for the iPhone market potential and what that means to Apple's bottom line.
Lots of cool-sounding tools for developers working with the SDK. Not being a coder though, I don't know if these are really valuable or a nice convenience. Regardless, EA apparently was able to build a full Spore evolution editor for the iPhone within two weeks when they had next to zero previous development experience on the Mac. Sounds impressive to me.
As expected, Apple themselves will be the only sanctioned way of getting SDK developed apps onto the iPhone. The good news is that the phone will have an "app store" application similar to the iTunes store. Apps can be acquired in iTunes and syced or wirelessly direct to the phone (WiFi or cell data network).
SDK available to anyone today. Beta of software update for devices (v2.0) going out today. Released to all customers in June. Same update for the Touch (SDK developed apps, eterprise features). Update for the touch will cost because they "account for the Touch differently." iPhone update will be free.
SDK available to anyone today. Beta of software update for devices (v2.0) going out today. Released to all customers in June. Same update for the Touch (SDK developed apps, eterprise features). Update for the touch will cost because they "account for the Touch differently." iPhone update will be free.
iPhone devs have to register with Apple's dev program for $99. Part of that will be Apple issuing them a digital certificate which will identify who an application's developer is. I would assume that right there might make it pretty tough (or at least not worth the effort) to get SDK developed apps onto the phone via any method other than the official Appple mechanism.
Trending Topics
After some further thought, the stuff announced today is almost more telling about Microsoft's priorities than Apple's. By licensing ActiveSync to Apple, Microsoft is competing directly with themselves for sales/licensing of their own Windows Mobile platform. That tells me Microsoft feels increased sales of Exchange Server and CAL licenses due to the iPhone could be more profitable than future sales/licensing of Windows Mobile.
i just got a windows mobile 6 phone, and man, is it ever painful to use compared to my Nokia, and especially atrocious when compared to the iPhone. I swear there's like 18button clicks to do anything, and no way to customize the menu order that I can find
Originally Posted by soopa
That's the idea behind an SDK, isn't it?
Originally Posted by Whiskers
Not sure....It sounds like its giving the green light for 3rd party developers to create apps, but they still aren't allowing people to open up the device as for as I know....
Originally Posted by Whiskers
Not sure....It sounds like its giving the green light for 3rd party developers to create apps, but they still aren't allowing people to open up the device as for as I know....
this is definitely awesome news, if they go 3G by June when the software updates come out, I will be selling my blackjack and picking one up. I love browsing the internet on my iPod Touch so I can't wait to have that in my pocket all the time.
Originally Posted by Billiam
After some further thought, the stuff announced today is almost more telling about Microsoft's priorities than Apple's. By licensing ActiveSync to Apple, Microsoft is competing directly with themselves for sales/licensing of their own Windows Mobile platform. That tells me Microsoft feels increased sales of Exchange Server and CAL licenses due to the iPhone could be more profitable than future sales/licensing of Windows Mobile.
Today was very good news for the iPhone I now may get one when my contract expires in May or I'll wait till June. They just need 3G and MMS and I'm sold. Flash would be nice too and the ability to edit Office docs but MS could add Office editing with the SDK now.
I don't see more businesses buying an exchange server just cause it works with the iPhone, I think more businesses will buy iPhones cause it works with Exchange.
Does someone want to explain what the iFund is cause I didn't get a good jist of it from reading Engadget?
I don't see more businesses buying an exchange server just cause it works with the iPhone, I think more businesses will buy iPhones cause it works with Exchange.
Does someone want to explain what the iFund is cause I didn't get a good jist of it from reading Engadget?
Last edited by #1 STUNNA; Mar 6, 2008 at 09:25 PM.
Originally Posted by #1 STUNNA
Does the iPhone work with hotmail?
PS: Dont get an iPhone, because the last thing I want is a thread from you about how you regret it, and love your zune phone...
Originally Posted by astro
i just got a windows mobile 6 phone, and man, is it ever painful to use compared to my Nokia, and especially atrocious when compared to the iPhone. I swear there's like 18button clicks to do anything, and no way to customize the menu order that I can find 

What kind of phone did you get and on what service?
Originally Posted by Billiam
From the bits that I've read the only thing that seems to be a no-no is the dock connector. Other than that, pretty much everything seems to be reachable by 3rd party devs. Accellerometers, multitouch gestures, OpenGL graphics, contact items, photos in the albums, etc...
Sounds like good stuff though....Can't wait until I get some apps on it.
Originally Posted by Sarlacc
Jesus, you just sit around day on MS's cock.
PS: Dont get an iPhone, because the last thing I want is a thread from you about how you regret it, and love your zune phone...
PS: Dont get an iPhone, because the last thing I want is a thread from you about how you regret it, and love your zune phone...
Originally Posted by Sarlacc
Jesus, you just sit around day on MS's cock.
PS: Dont get an iPhone, because the last thing I want is a thread from you about how you regret it, and love your zune phone...
PS: Dont get an iPhone, because the last thing I want is a thread from you about how you regret it, and love your zune phone...
Couple of Mail related tidbits about 2.0 that were apparently in the press release but not mentioned during the event yesterday:
-Mail will gain the ability to view PowerPoint files similar to what it can now do with Word docs
-Mail will also gain mass delete and move features
-Mail will gain the ability to view PowerPoint files similar to what it can now do with Word docs
-Mail will also gain mass delete and move features
Originally Posted by soopa
Welcome to 2008.
Jobs really hit it out of the park on this one.
Originally Posted by h2o-pr00f
Some of the apps 3rd party companies were able to make in 2 weeks with the sdk are pretty sweet.. the AIM.. and the 3D games 

Originally Posted by Gizmodo
The enthusiastic high-fives of future iPhone instant messaging users yesterday might be quite a bit less enthusiastic today when they find out that Apple is not going to allow user-made SDK applications to run in the background. This means every application, from IM to VoIP to GPS mapping, will have to terminate entirely when the user switches out to take a call or change a song. How does this affect you? It means you won't be a be able to receive IMs unless you're currently inside the IM app, forcing you to disconnect when you take a call. There's an upside and a downside to this decision.
First, we already know that apps running in the background as a process is possible on the iPhone. The iPod app, SMS app, and various other apps all run in the background now and continue running no matter where you go in the phone. Also, user-made Installer.app apps like Apollo (an IM client) already run in the background just fine. So why did Apple make this limitation that all apps have to quit whenever the user switches out? Memory management. From Apple's Human Interface Guidelines for the iPhone:

Apple has no idea what combination of applications you could possibly install on your phone, and they can't control it. If you were to install two apps that took up loads of the iPhone's memory (we're talking RAM), and they both ran in the background, it would slow down the phone's other, more important tasks such as calling or iPodding. If this were the case, Apple would be blamed for making a slow or non-responsive phone even when it's not actually Apple's fault. This is exactly the thing that goes on in Windows Mobile devices. It's fine when you're just running normal, natively-installed apps, but when you get to multi-tasking with your own installed programs, the phone becomes sluggish and everyone curses Microsoft. Apple wants none of this.
So the implication to you, the end-user, is that you can't have apps running in the background, constantly checking the internet. This means no RSS reader that's always up-to-date and no IM apps that always sit in the background, listening for messages. If you're wondering Exchange's push email and calendars are going to work in this scheme, it'll be integrated into Apple's first-party Mail system, which can be allowed to run in the background.
But in the end, it's only a small portion of apps that are really affected by this rule. Games or utilities can save their app status to disk often so that you can resume where you left off when you start it back up. But until the iPhone allows SDK-applications to run in the background, you're probably better off using a web-based chat application in Safari (which already has permission to).
First, we already know that apps running in the background as a process is possible on the iPhone. The iPod app, SMS app, and various other apps all run in the background now and continue running no matter where you go in the phone. Also, user-made Installer.app apps like Apollo (an IM client) already run in the background just fine. So why did Apple make this limitation that all apps have to quit whenever the user switches out? Memory management. From Apple's Human Interface Guidelines for the iPhone:

Apple has no idea what combination of applications you could possibly install on your phone, and they can't control it. If you were to install two apps that took up loads of the iPhone's memory (we're talking RAM), and they both ran in the background, it would slow down the phone's other, more important tasks such as calling or iPodding. If this were the case, Apple would be blamed for making a slow or non-responsive phone even when it's not actually Apple's fault. This is exactly the thing that goes on in Windows Mobile devices. It's fine when you're just running normal, natively-installed apps, but when you get to multi-tasking with your own installed programs, the phone becomes sluggish and everyone curses Microsoft. Apple wants none of this.
So the implication to you, the end-user, is that you can't have apps running in the background, constantly checking the internet. This means no RSS reader that's always up-to-date and no IM apps that always sit in the background, listening for messages. If you're wondering Exchange's push email and calendars are going to work in this scheme, it'll be integrated into Apple's first-party Mail system, which can be allowed to run in the background.
But in the end, it's only a small portion of apps that are really affected by this rule. Games or utilities can save their app status to disk often so that you can resume where you left off when you start it back up. But until the iPhone allows SDK-applications to run in the background, you're probably better off using a web-based chat application in Safari (which already has permission to).











.