Iterate 1.1.2 is Available in the App Store
Today we released an update to Iterate, our iPhone client for Pivotal Tracker.
This small bug fix to Iterate extends our timeout (or the amount of time that we wait for a server to respond to a request for information).
Iterate is great because right from your iPhone you can:
- Access your projects on the go including your Current Iteration, Backlog and Icebox. (To access everything you need to turn on some goodies in settings)
- Update the status, estimate or owner of a story.
- Add a label, note, task or attachment to a story.
- Mark tasks as being complete.
- Add a new story to your Icebox.
- Start a story in your Backlog or Icebox.
If you are using Iterate please check out the settings. We have turned off a lot of features that consume data to ensure that people with large projects don’t have trouble - but if your projects are smaller there are some goodies you can turn back on.
What’s Next?
At this point we’d really like to hear from people using Iterate to know what direction we need to take next.
We think we have the best app out there for accessing Pivotal Tracker on the go. But that’s just us. What do you think?
How can we make Iterate better?
Rogers 3G/3.5G runs on 850/1900
No matter what people tell you about phone compatibility, you need both bands to be sure you will get full coverage. Full details on the GSMA website.
If you poke around you’ll see that Rogers also owns some 1700 spectrum. It is not in use at this point in time.
Also, the GSMA seems to think that Fido operates their 3G on 2100 but I am under the impression that this is not the case - they use 850/1900 just like Rogers.
The Punchline
If someone is trying to sell you an unlocked phone and you want to use it in Canada it needs to have the 850 and 1900 bands.
The Nexus One WiFi Issue
I read an article on BGR on users reporting WiFi issues with the Nexus One.
I actually am experiencing the issue - so let me provide some insight.
The Problem: Reconnecting to WiFi
When the Nexus One goes to sleep (turns off it’s display) the default behavior is to disconnect from WiFi - I assume to save power. When you wake the device back up it is supposed to connect to your WiFi network automatically. The problem is that this never happens.
The Nexus One gets itself into a state where is disables reconnections to the WiFi network and won’t try to connect again unless prompted: this can include rebooting, turning WiFi off then on again, or telling it to connect to the network.
Part of the issue seems to involve leaving the home-screen before WiFi connects. Could be coincidence - not sure.
Another potential coincidence is that I don’t seem to experience the issue at my office. Pretty much the same WiFi both places though, Apple AirPort Extremes. The only difference might be Airport versions.
This is Actually a “New” Issue
What do I mean by that? The Nexus One in question is actually my second and my original Nexus One did not exhibit this behavior. It would connect to WiFi without prompting.
This doesn’t mean it is hardware related. But it could very well be. Equally likely that a firmware issue can fix it.
The Solution
There isn’t one at this point short of installing a 3rd party app that reconnects you once your WiFi drops out.
Hope Google gets to the bottom of this one soon.
UPDATE
It appears to be a chipset issue after all involving the WiFi sleep mode and certain routers. It is also the case that it should be fixable in software.
Android 2.2 Previewed at Google IO
Well, it was more than previewed - Google actually let it out into the wild for a bit where Nexus One users with the AWS version of the phone (think T-Mobile or WIND) were able to update.
The update has since been pulled (search and ye shall find, though) but I tossed it on my Nexus One and gave it a once over.
Tethering FTW
Android 2.2 adds WiFi tethering. This really is the killer feature, especially if you are packing a WiFi only iPad.
It is super simple to setup and works like a charm.
Flash Support (Not that I want it.)
Android 2.2 also adds support for Flash - not that I’d suggest installing it or turing it on.
Of the three people that cheered when this was announced, two work for Adobe and one makes CPU hogging Flash ads for websites.
GUI Updates
Google is starting to add a bit more polish to the Vanilla Android GUI. For example, quick access to your phone or browser is now available from the home screen.
I would expect this to be kicked into overdrive with Android 3.0 whenever we see it. Google has hired a key player from Palm’s WebOS team and I would expect that to significantly improve the look of the stock Android OS.
Nexus One and Android
The killer combo really comes from two things, hardware and software.
Hardware
If you have ever held a Nexus One you know the hardware is amazing. HTC really knows how to make a great phone that is sleek and sexy. The OLED display is the best I have seen on a phone.
Software
Android is the perfect OS if you are a GMail or Google Apps user. There simply isn’t another platform besides Android that does justice to GMail in a mobile environment.
The Punchline
When you combine great hardware with great software you win. The experience would be perfect if it didn’t look like Google.
Disclaimer
Look, I am totally making this all up. I have no idea what Adobe or Apple is thinking.
However, in my twisted imagination, this is how this whole Flash/iPhone situation went down…
I can imagine the conversation…
This is how I imagine the conversation going a couple years ago when Adobe first tried to bring flash to the iPhone:
ADOBE: So, how about adding flash support to the iPhone?
APPLE: Yeah, no thanks. We’re not really crazy about how it works on OSX.
ADOBE: Um, pretty please.
APPLE: Yeah, no.
ADOBE: What if we build a Flash cross-compiler that creates native iPhone Apps. That will be much better, right?
APPLE: Still no.
ADOBE: Well, just in case you change your mind we’ll build one anyways.
APPLE: Don’t call us. We’ll call you…
Why the surprise?
I am not sure why anyone, including Adobe, is surprised about the announcement. I cannot image a world where Apple would let this happen. They said “NO” to Flash on the iPhone browser - why would this be different.
This really is the main thing that gets me: I can’t believe that Adobe had the expectation that Apple would just sign off on this. I am going to assume that they new this all along. So then the real question is: why build and publicize a feature that Adobe KNOWS is going to be rejected by Apple?
And, why build something you KNOW Apple will reject?
Let’s pretend to be Adobe. Years of being on 99.9% of all browsers and then two things happen: Apple publicly denounces support for Flash on their Mobile platform (which is really starting to pick up steam) and people really start talking about Flash alternatives and HTML5.
That is not going to make you happy. iPhone, arguably the most advanced mobile platform ever, thumbing it’s nose at Flash. It is going to be hard to explain that one to the investors. Apple and Adobe have a difference of opinion on this but it is Apple’s closed device.
Well, if Adobe can’t convince Apple to put Flash on the iPhone, maybe public opinion can. So Adobe starts making its concerns public in an attempt to get support. And while a lot of people agree with them, a lot of people who are tired of Flash crashing their browser start talking about that, and suggest it was simply time to upgrade to HTML5 anyways. Poor Adobe, if anything now HTML5 has more support.
And this is the point where Adobe decides to build a tool that they KNOW is going to get rejected. If they show it off to developers and get them excited maybe this will be enough.
So they build a Flash-to-iPhone compiler and make it the tentpole feature of Flash CS5 in the hopes public opinion will sway Apple in ways that they cannot.
Days before they can launch Apple explicitly forbids the use of Flash. And the public reacts.
How will a Flash/iPhone compiler help me?
It won’t. The App Store is full already. It is bursting at the seams with Apps.
There may be some developers or publishers that have been waiting for Flash but they have other options. And while those options likely increase the complexity and cost of development they also encourage developers to make apps that are specifically tailored to the iPhone or iPad.
Most (if not ALL) of the time Apple’s tools will make a better App.
Won’t this help me as a developer?
Nope. It will just lower the bar. It will mean anyone that can use Flash can now publish an App. It will get more Apps in an already difficult to navigate store.
Differentiation is what allows you to charge for your App.
The harder it is to create an App the bigger the potential reward for those who do it.
Is this going to work?
Nope. And as far as I can tell it will likely backfire (if it was done for these reasons I imagine).
Steve Jobs isn’t the sort of guy that public pressure works on. He is driven by a purpose larger than public opinion. Apple is driven by this same purpose.
It is going to backfire because Adobe has inadvertently started a debate about the relevancy of Flash. And I don’t think they will be happy with the results. If I was a betting man I would bet on HTML5.
The Punchline
Why develop something that Apple will reject? Clearly this is a posturing attempt by Adobe to get more public support for their efforts to maintain the relevance of Flash.
And I think it will be later known as a tactical error.
