Final SDK build available (84853); deadline extended to Tuesday, August 5?????

[xingye]

What's this????????

ADC Entrants,

We're pleased to announce that SDK build 84853 is now available on
your private download site. This will be the last build released for
ADC Round 2 and is the build that you will need to submit your final
application under.

In addition, the final ADC deadline has been extended to Tuesday,
August 5. This is the final ADC deadline.

Thanks!
Android Developer Challenge Team

[Hong]

they seemed to send to the wrong mailing list, haha

[Shane Isbell]

No way Google meant to send this to a public list, as it contains information about the SDK.

 

Shane

[差沙]

this is the newest version? how to download

[xingye]

details of the mail

maybe i'm in the entrants list but i don't know it, ha:)

from Android Developer Challenge Team <android...@google.com>
to Android Developer Challenge Contest Entrants <adc-
entr...@google.com>
date Tue, Jul 15, 2008 at 5:50 AM
subject Final SDK build available (84853); deadline extended to
Tuesday, August 5
mailing list adc-entrants.google.com Filter messages from this mailing
list

[Gothy]

Nice :)

[Rui Martins]

This just looks as another weird form of leaking propaganda.

[Johan de Koning]

If this is the latest build for ADC Round 2, why not make it available
for all developers?

[smallgroup]

I don't know what happened

> > This just looks as another weird form of leaking propaganda.- Hide quoted text -
>
> - Show quoted text -

[Hong]

just trying to get the rest of us excited... that Android still has some progress...

[NY]

I receive the mail too...and don't no where is the private download
site

[plusminus]

It way a mistake.
kinda "Accidential E-Mail-App Autocompletion".

[InakaBoyJoe]

Ahhhhh, now it makes sense. So they've been making private SDK
releases while the rest of us suffer with the pile of bugs from the 4+
month old release.

And then "leaking" this information is their way of telling us, "We
really only need about 50 apps for the platform, so the rest of you
can just go develop for iPhone."

Great, just great.

[Anthony]

I got the same email too, don't know its meaning.

[rezar]

I hope they make it available for every body, at least member of that
email lists.

[David McLaughlin (Android Advocate)]

Hi everyone,

As some pointed out, I accidentally sent the note concerning ADC Round
2 entrants to the wrong list. Sorry for the annoyance.

Thanks,
David

[Johan de Koning]

David it is not a problem. Just send us the latest version of the SDK
and we forgive you :D

I was watching the Google IO presentations about Google Android.
Things like it is an open platform. But when you receive an email
about a specific group can only have the latest SDK and the other
should still work with the old version, you are wondering what open
means.

On 15 jul, 17:48, "David McLaughlin (Android Advocate)"

[Josh Guilfoyle]

To clear things up for those who were not in the loop early on.
Google has required the ADC round 1 winners to sign an NDA to get
access to newer versions of the SDK. For unknown reasons, Google has
elected not to make this decision public. Several developers and
developer advocates have commented loosely on this decision, generally
explaining that we should not expect a new public SDK, but that one
will drop some time before handset launch.

The e-mail you all received was an accident, but is essentially an
admission of this policy. It will be interesting to see if Google now
decides to formally comment on the private SDK releases.

On Jul 15, 8:48 am, "David McLaughlin (Android Advocate)"

[daspears]

My (somewhat) poetic appeal (posted here recently and repeated below)
didn't get us anywhere.
Personally, I'm heading over to iPhone development.

We know you are busy
toiling away
You've got issues to solve
without delay

Embedded OSes are
not like web apps
Firmware must update
without a hitch
Else millions of customers
will suffer the glitch

Your schedules are tight,
the handsets cant wait
You have to release
in 4Q O-Eight

We do wish you luck
as you test through the nite
and code through the day
But...
Could you please please just
give us a new SDK?

-Dave

p.s. We don't mind if its buggy
and not tested so well
the old SDK
is giving us hell.

[Shane Isbell]

On Tue, Jul 15, 2008 at 1:13 PM, daspears <daspea...@yahoo.com> wrote:

My (somewhat) poetic appeal (posted here recently and repeated below)
didn't get us anywhere.
Personally, I'm heading over to iPhone development.

The Apple App Store did 10 million downloads in the first five days. Android has a long way to go in a very competitive field. Without developer support, Google and the carriers are going to need one hell of a consumer product.

 

Shane

[Jon Webb]

This explains something I've wondered about for a while. Back before
the competition I tried to build an app and couldn't get basic things
(like reading past byte 16384 of a file) working. I reported a bug,
provided an example, the whole thing. The bug and a lot (like
hundreds) of other bug reports were reviewed. But then they were never
fixed. Couldn't finish the app. Fine, whatever, I'll wait for the
phone.
I thought it was odd there were no further SDK updates -- what was
going on? Was Android delayed or canceled? Were they trying to make a
really good, complete release before they came out with something?
Now I know. They decided to work closely with a few developers and to
give them an advantage over everyone else. Could be there's a
reciprocal agreement with those developers to give them better support
in exchange for their app development work.
It's not an unusual move in software development. Not particularly
nice not to make it public, though. Just leaves the rest of us
hanging, waiting for an SDK update that never comes.

[Shane Isbell]

The next time Google comes out with some big project asking for developer support and talking about openness, we will know not to trust them. Time to move on.

 

Shane

[Jon Webb]

Not that Apple is that much better. No Java, no plans for it. They are
way ahead in terms of hardware and SDK stability, but Objective C is
platform specific and much harder to use than Java.
Every cellphone maker wants to control the market and keep the app
market open to themselves and their partners. They're all terrified
that what happened to IBM in the PC market will happen to them.
Some day a cellphone platform will come along that enables real
application development on a stable platform available from multiple
manufacturers. (That's what I'd hoped Android was.) Then the market
will really take off. Until then, we're stuck with fragmentation, like
PC app developers before Microsoft crushed everybody.

On Jul 15, 4:26 pm, "Shane Isbell" <shane.isb...@gmail.com> wrote:

[george_c]

Why Google?

Why don't you voice your opinion and for gods sake stop just sitting there reading what we post?
Get your role right and show us you have some leadership to the crew(us developers).
If anyone is going to make it happen, its this community of developers.

The more silent you remain, its in human nature to trust less.   IMHO, you're bordering to recover!

George

[Jon Webb]

There's a petition about this at
http://groups.google.com/group/android-discuss/browse_thread/thread/957fa043e2a199b6.
-- J

On Jul 17, 4:51 pm, george_c <chrisg...@gmail.com> wrote:
> Why Google?
>
> Why don't you voice your opinion and for gods sake stop just sitting there
> reading what we post?
> Get your role right and show us you have some leadership to the crew(us
> developers).
> If anyone is going to make it happen, its this community of developers.
>
> The more silent you remain, its in human nature to trust less.   IMHO,
> you're bordering to recover!
>
> George
>

> On Thu, Jul 17, 2008 at 9:58 PM, Shane Isbell <shane.isb...@gmail.com>

> wrote:
>
> > The next time Google comes out with some big project asking for developer
> > support and talking about openness, we will know not to trust them. Time to
> > move on.
>
> > Shane
>

[Denis Rybakov]

Google, fuck yourself and your android.

RIP