No, I disagree. The problem is, that a cute developer has build an app with a feuture set no other can beat. GS is not able to offer an app with nearly the half of the features and while they say they use their own API the question comes up what the API can offer to a developer? For me it seems, that the API is the lack. As I remember, carnero would rather use the API for his app if it would support the needs for his app. You can't develop against an API when there's no way to realize functions while they are not supported. For that he decided to use another way, I guess just to demonstrate what's possible. From that point of view, I can understand how frustrating it must be if you want but can't. Maybe he hasn't the patience, a single person can act much more agile than a complete team in a company. Maybe it's only a big misunderstanding, who knows?
I disagree again! The gap is between the market demands resulting in requirements that the API can't serve. It has nothing to do with GS' iOS app. If you compare the iPhone app (works well so far) with c:geo, you will find out that c:geo serves user's need much better. OK, Android users are in general different from iOS users due to not comparable philosophies.
The core question to me is if GS' API could satisfy the requirements of c:geo or not. I guess no, at least not yet. If the answer is 'not yet', when will the API be ready? If the answer is 'no', what set of fuctions will GS offer to other developers? If you think ahead the comparison with A**le is not so far away since A**le has really strong restrictions of what developers are allowed to do and what not.