Obviously the people in the top 50 of the Challenge are those that have really figured out Android, and their feedback will be much more valuable than the feedback from the community at large. Narrowing the group down to them until the final release helps to focus resources.
Personally, I have focused on design of my app, and not coding until I see the final release, so it fits in with my plans perfectly :). Anyone doing coding now has to expect to redo their code with every release they want their app to run on, and I don't have the time to do that anyway.
Southfield, MI, USA
If you get today's work done today, but do it in a way that you can't possibly get tomorrow's work done tomorrow, then you lose.
This e-mail or communication, including any attachments, is intended only for the person or entity
to which it is addressed and may contain confidential and/or legally privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is prohibited. If you received
this message in error, please contact the sender immediately and permanently delete all copies,
electronic or other, you may have or from your computer. Any disclosure, copying, distribution,
reliance or use of the contents or information received in error is strictly prohibited.
The foregoing applies even if this notice is imbedded in a message that is forwarded or attached.
LOL, I got excited when I saw this email, but I'm guessing it was
mistakenly sent to losers. Unless now they're just taunting us for
Google And Blog
From: YA [mailto:yuri.a...@gmail.com]
Sent: Monday, July 14, 2008 3:05 PM
To: Android Discuss
Subject: [android-discuss] Final SDK build available (84853) deadline
extended to Tuesday, August 5
Google has selected a small group of very committed Android developers to help them test the SDK and get it to a final release.
Obviously the people in the top 50 of the Challenge are those that have really figured out Android, and their feedback will be much more valuable than the feedback from the community at large.
This is very long.
Shane Isbell wrote:
> Google is closed
A drop of much of the source code is available in a repository and in
tarballs. It runs on Linux. It has a free (pre-alpha) SDK. People have
been able to take it and get it running on a variety of unsupported
hardware, such as the Nokia N800/N810.
On the open spectrum, today, it is more open than Apple, Microsoft,
Blackberry, or even Symbian. It is less open today than LiMo and
OpenMoko. If -- *if* -- they keep their promises, it'll be as open as
LiMo and OpenMoko by year's end. With luck, Symbian will wind up this
open as well.
It is definitely more closed -- today -- than it was a few months ago.
That is definitely worthy of angst and anger, but only to a point.
> Google is not really even a leader anymore, they are following
Android is following lots of people: Apple on the sizzle side,
LiMo/OpenMoko on the free side.
Depending on your belief in the latter two platforms, Android *might* be
the longer-term leader in free, if it can use the energy from the sizzle
to be a "playa" bigger than LiMo or OpenMoko. It's even conceivable they
could wind up the leader in sizzle too -- just because *we* don't see
progress doesn't mean progress isn't happening.
> More fragmented market?
That barn door's been open for years. If you're looking for a
monoculture, try the desktop PC marketplace on for size.
> The carriers get a free operating system built on the hard work
> of the open-source community.
If you mean Linux, Android isn't the first or only Linux-based mobile
phone OS, and it probably won't be the last.
> We already have CDC and CLDC platforms if we want to do Java, with a
> market that already exists.
Considering that Microsoft doesn't like CDC/CLDC, and Apple doesn't like
CDC/CLDC, and Android's given no indication of liking CDC/CLDC, and I
don't see any CDC/CLDC activity with LiMo or OpenMoko, I'm not too
bullish on CDC/CLDC. But, hey, I've definitely been wrong before.
Android is making a series of related mis-steps here, from the private
SDK releases to the lack of communication. Somebody, somewhere, needs to
be fired, or worse, needs to let me rip them a new one. If Android
fizzles, which is entirely possible, this whole mess will be one of the
bullet points as to why.
And, if Android is able to carve out a significant chunk of the market,
few will remember this fiasco in four years' time, other than a general
sense of unease whenever symptoms like we're seeing now happen to pop up.
In this respect, Android is going through some of the same stumbles that
Netscape did when they "released" Mozilla (big code dump, diddly-squat
for support), or when Sun released OpenOffice.org (big code dump,
license soup, mixed messages from management), or IBM did when it
released Eclipse (big code dump, general sense of "uh, now what?").
Those projects went on to be successes, by most measures.
Of course, the same stumbles befell Real Networks with the release of
Helix (big code dump, godawful license I have the shame of being
involved with), SAP with the release of SAP DB (big code dump, little
community building), and so on. There is no way to determine, here and
now, how this will play out for Android.
The only thing I know for certain is that rehashing the same complaints
again and again and again won't exactly help Android's cause any. Given
the press coverage to date, I feel fairly certain that the "we're
<bleep>ing unhappy" message has made it up the Mountain (View). Maybe
they'll respond now, maybe they'll stay the course until the ADC wraps
in three weeks, or until the product ships in a few months.
Zero days, three weeks, three months -- none of it really makes much
difference. Any, perhaps all, open source communities are marathons, not
sprints. As for me, I'm just staying limber.
Mark Murphy (a Commons Guy)
Warescription: All titles, revisions, & ebook formats, just $35/year
Odds are you're right. However, don't you think it's just a trifle early
to make that a definitive claim? Seeing as how the ecosystem hasn't been
launched yet? I mean, as much as the early community-building was slick
and all, the gun doesn't truly sound until devices are ready, as far as
> And yes, J2ME
> (CDC/CLDC) did very well. Good for those on the inside track, miserable
> for the individual developer.
I hear ya on the misery part. Complete with Kathy Bates and a
sledgehammer, IIRC. ;-)
> But I'm not Google, I'm a
> developer, sitting there feeling cheated, lured into what seemed to be a
> thriving community before Google cut it off at the knees.
I'm certainly hoping this is an interregnum, and we'll be in position to
raise the community anew shortly. But, I may be wrong, in which case
I'll look upon 2008 as being a bit of a lost year. C'est la vie.
> I'm on the outside, waiting, wondering if this is really the new mobile
> ecosystem, when it reeks of the old.
Simple: don't invest much in it just yet.
Early adopter-hood is not always a river of milk and honey. In fact, I
suspect that more often than not, early adopter-hood is a whole lotta
cow pies and bee stings first.
If things turn positive again, there will be plenty of room for all
sorts of folk in the community. If it turns completely south, you won't
be out much.
There will be some morons, like myself, who will try to double-down
during the hard times and hope it pans out. There's all sorts of
strategies for dealing with the situation.
Frankly, what gets my goat isn't the fact that people are jumping off
the bandwagon, or even that they're announcing they're jumping off the
bandwagon. It's that they are *repeatedly* announcing they're jumping
off the bandwagon and thereby attack the bandwagon on their way to stage
> And as for open-source projects being a
> marathon, perhaps that's true but running blindly forward hoping that
> one is running in the right race or in the right direction may not be
> the wisest course;
As a wise man once said, "Sometimes, ya gotta roll the hard six."
Well, OK, a wise character on a TV show.
> and don't forget Pheidippides didn't live through his
Yeah, yeah, yeah, those who don't learn from history are doomed to do
I'm not asking anyone to run the marathon who doesn't want to -- just
don't toss caltrops into the road for those who run now and those who
choose to run in the future.
What I'm seeing is the occasional trickle of messages, then a whole batch
of them in one shot, some fairly old. For example, your message came in as
a part of a group of nine new ones. I think yesterday I got a flood of
about two dozen all at one time.
I'm not signed up to get individual emails from other Google Groups, so I
have no idea if this is system-wide or what -- anybody know?
Mark Murphy (a Commons Guy)
_The Busy Coder's Guide to Android Development_ -- Available Now!