Good Job Bob
Member
Sparrow for iPad should be great.I think everyone should work on a good E-Mail client first.
Whenever that comes out.
Speaking of Sparrow, I hope iOS 6 allows it and other apps to utilize push notifications
Sparrow for iPad should be great.I think everyone should work on a good E-Mail client first.
They already can, if they pay for their own servers.Sparrow for iPad should be great.
Whenever that comes out.
Speaking of Sparrow, I hope iOS 6 allows it and other apps to utilize push notifications
They really shouldn't have to pay for their own servers.They already can, if they pay for their own servers.
Why not?They really shouldn't have to pay for their own servers.
Small startups shouldn't have to worry about servers and security and etc.Why not?
I may be wrong (I just glanced at the iOS SDK just now so I don't think I'm wrong), but I'm sure Apple does not provide a push API for VoIP apps. They provide an API for the app to keep running in the background and listen for calls. They should only allow that for limited use cases--keeping Sparrow running and listening for e-mails (and then sending local notifications) is more battery-intensive than receiving push notifications over the air once in a while when e-mails are received. Otherwise apps will be using it to run in the background for something silly and battery-draining like Twitter, IRC or instant messaging, or even if you happen to open multiple e-mail apps.Small startups shouldn't have to worry about servers and security and etc.
Apple already provides a push API for VoIP apps, if they opened that up to all apps everyone would benefit.
I admit that I'm not wildly familiar with iOS development, so here's what Sparrow says:I may be wrong (I just glanced at the iOS SDK just now so I don't think I'm wrong), but I'm sure Apple does not provide a push API for VoIP apps. They provide an API for the app to keep running in the background and listen for calls. They should only allow that for limited use cases--keeping Sparrow running and listening for e-mails (and then sending local notifications) is more battery-intensive than receiving push notifications over the air once in a while when e-mails are received. Otherwise apps will be using it to run in the background for something silly and battery-draining like Twitter, IRC or instant messaging, or even if you happen to open multiple e-mail apps.
However, Apple provides an API that allows an app to be woken up in case of a network event meaning it is virtually connected at all times like Sparrow on the Mac. For example, VoIP (Voice over Internet Protocol) apps take advantages of this specific API so you can receive calls even when the app isn't opened.
It's not. The VoIP background task doesn't keep the app open. It just monitors the app's sockets for incoming calls. Something like that could be implemented for email clients.I admit that I'm not wildly familiar with iOS development, so here's what Sparrow says:
Maybe I'm reading it wrong or he didn't explain everything, but it doesn't seem the app is open in the background.
The app is waken up when the sockets are opened though, and a background task is performed. It still is more battery-intensive than push, especially if opened to all apps. It's nothing like a VoIP Push API like some sites are claiming.It's not. The VoIP background task doesn't keep the app open. It just monitors the app's sockets for incoming calls. Something like that could be implemented for email clients.
That's true, but the Sparrow devs showed some interesting caveats about push email regarding security. I don't know if it would be the best option for a small startup, regardless of its efficiency over the VoIP implementation.The app is waken up when the sockets are opened though, and a background task is performed. It still is more battery-intensive than push, especially if opened to all apps. It's nothing like a VoIP Push API like some sites are claiming.
I also don't think they're going out of their way to allow email apps to have a background task running alongside their own email background task (where normal push, which is less battery-draining than a constant socket monitor, already is a cause for a lot of battery drain). It seems like a perfect item where Apple wants devs to use push for less battery drain, and has no intention of giving a leg up to competitors to their own email app.That's true, but the Sparrow devs showed some interesting caveats about push email regarding security. I don't know if it would be the best option for a small startup, regardless of its efficiency over the VoIP implementation.
Setting default applications is actually on my wish list.I also don't think they're going out of their way to allow email apps to have a background task running alongside their own email background task (where normal push, which is less battery-draining than a constant socket monitor, already is a cause for a lot of battery drain). It seems like a perfect item where Apple wants devs to use push for less battery drain, and has no intention of giving a leg up to competitors to their own email app.
iOS needs huge changes. It's Frankenstein's monster.
In lieu of that, iOS 6 at least needs to fix this:
* Shit-shit multitasking (how is Apple the only company to get the UI wrong on this?)
* No universal access to common settings (again, only Apple is failing)
* Maps experience is miserable compared to Android
* Siri does far less now than when it was a 3rd party app that ran on all iOS devices
* Siri is usable on a reliable WiFi connection, and in virtually no other circumstance
iOS needs huge changes. It's Frankenstein's monster.
In lieu of that, iOS 6 at least needs to fix this:
* Shit-shit multitasking (how is Apple the only company to get the UI wrong on this?)
* No universal access to common settings (again, only Apple is failing)
* Maps experience is miserable compared to Android
* Siri does far less now than when it was a 3rd party app that ran on all iOS devices
* Siri is usable on a reliable WiFi connection, and in virtually no other circumstance
They really shouldn't have to pay for their own servers.
On the contrary, it needs almost no changes. They're going to continue selling like hot cakes regardless.. they don't need to make drastic changes right now; no one is asking for it.iOS needs huge changes.
On the contrary, it needs almost no changes. They're going to continue selling like hot cakes regardless.. they don't need to make drastic changes right now; no one is asking for it.
Oh right :-(You mean later in the fall, right? The only hardware I ever remember being unveiled at WWDC are iPhones, and those are now fall introductions. iPod touches were usually at the fall music events.
Har har. My point was it doesn't need HUGE changes as Utako was indicating; there's no need to reinvent the wheel.The iPhone 3GS still sells like hot cakes. Clearly they don't need to make any more changes.
Windows XP sold like hotcakes. Clearly Microsoft didn't need to make any changes to IE6.
By the way, Apple doesn't make what people are asking for. Apple makes what people don't know they want yet.
Har har. My point was it doesn't need HUGE changes as Utako was indicating; there's no need to reinvent the wheel.
In fact, making too many changes could be a downside to those who have just begun getting accustomed to iOS 5.
I'm guessing the changes they bring will be generally safe bets, nothing that drastically changes the way people use their devices now.
The dumbfuck Apple user in me is probably happy with iOS, it's the tech enthusiast in me that screams for more.haha people still write about Apple as if they know how to run Apple better than Apple.
And what a disappointment iOS 5 turned out to be. I said keep it low profile, so no one will notice when Apple passed another x.5 release as major update.Wasn't the rumor mill for iOS 5 spinning wildly around this time last year? We've heard nothing this year outside of a revamped app store.
The dumbfuck Apple user in me is probably happy with iOS, it's the tech enthusiast in me that screams for more.
And what a disappointment iOS 5 turned out to be. I said keep it low profile, so no one will notice when Apple passed another x.5 release as major update.
Look who's talking. :lolWhy the inflammatory remarks? You're better than that.
lolLook who's talking. :lol
I'll do better next time. Promised. <3
Safe bets are what kill ecosystems. If you are catering to keep your users comfortable, someone is going to disrupt the shit outta you because they don't have that constraint. Seen it happen in the space far too many times with PalmOS, RIM, Window CE, Nokia Series 60, etc. When the tipping point happens, and it always does, you can never recover because the core concepts of what disrupted the shit outta you doesn't exist in your platform because you didn't want to take people from their comfort zone. Apple is dangerously dangerously close to being in that boat. As a developer for iOS and Android I would definitely say the Galaxy Tab 2 7" is a better platform for innovation than iOS. Its just overly complicated for the average user which is a huge detriment.
Fuck Sparrow on iPad, Tweetbot on OS X has to happen now.
+1.Anyone who thinks iOS needs an overhaul is wrong. The end.
Anyone who thinks iOS needs an overhaul is wrong. The end.
Hmm what's the over under on new Macbook Airs being announced/released around then? It's time right?
Yeah, except Ballmer didn't have 300+ million Windows OS devices in circulation, did he? Apple can't be put under the same rules that other companies are forced to go by, any more.I'm sure Steve Ballmer said the same about Windows Mobile at some point.
"I works fine"
"It does this and this well"
"Users don't really want that"
"We'll continue to innovate"
must.... resist.... but... can't
IMG]http://www.culturebully.com/wp-content/uploads/2009/10/converge-jane-doe.jpg[/IMG]
Yeah, except Ballmer didn't have 300+ million Windows OS devices in circulation, did he? Apple can't be put under the same rules that other companies are forced to go by, any more.