I'm starting this petition, to express my personal frustration about
the release cycles and the information policy of the Android SDK.
Before m5 we were waiting about 2 months, now we are waiting almost 4
months!
Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
built-in Geocoding are not working.
In order not to lose many highly encouraged developers, I think its
time to release some news about the development process of the SDK.
Maybe let us know why we have to live with these long cycles.
As you maybe know, I am one of the biggest fans of Android, putting a
lot of work into the community through my forum. But unfortunately
disappointment is being born in the last weeks :(
(Especially thinking of recently existing OpenMoko-Phones and the new
iPhone SDK).
In my personal opinion it is not the right choice to keep developers
in the dark. We, the developers, are the absolute base of success to
the whole Android platform. The presentation with GoogleIO was a good
first step but for me it was nto enough.
Therefore I am 'signing' this 'petition', hoping to receive
information/update on the Android SDK.
(+1) plusminus
Regards, plusminus
http://anddev.org # Worlds largest Android Development Community / Tutorials
PS: I didn't want to depreciate the work of the Android Dev Team or
anyone else.
On Sat, Jun 28, 2008 at 3:27 PM, plusminus <stoeps...@gmx.de> wrote:
> Hello everyone,
> I'm starting this petition, to express my personal frustration about > the release cycles and the information policy of the Android SDK. > Before m5 we were waiting about 2 months, now we are waiting almost 4 > months! > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like > built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its > time to release some news about the development process of the SDK. > Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a > lot of work into the community through my forum. But unfortunately > disappointment is being born in the last weeks :( > (Especially thinking of recently existing OpenMoko-Phones and the new > iPhone SDK).
> In my personal opinion it is not the right choice to keep developers > in the dark. We, the developers, are the absolute base of success to > the whole Android platform. The presentation with GoogleIO was a good > first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive > information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminus > http://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or > anyone else.
> On Sat, Jun 28, 2008 at 3:27 PM, plusminus <stoeps...@gmx.de> wrote:
> > Hello everyone,
> > I'm starting this petition, to express my personal frustration about
> > the release cycles and the information policy of the Android SDK.
> > Before m5 we were waiting about 2 months, now we are waiting almost 4
> > months!
> > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> > built-in Geocoding are not working.
> > In order not to lose many highly encouraged developers, I think its
> > time to release some news about the development process of the SDK.
> > Maybe let us know why we have to live with these long cycles.
> > As you maybe know, I am one of the biggest fans of Android, putting a
> > lot of work into the community through my forum. But unfortunately
> > disappointment is being born in the last weeks :(
> > (Especially thinking of recently existing OpenMoko-Phones and the new
> > iPhone SDK).
> > In my personal opinion it is not the right choice to keep developers
> > in the dark. We, the developers, are the absolute base of success to
> > the whole Android platform. The presentation with GoogleIO was a good
> > first step but for me it was nto enough.
> > Therefore I am 'signing' this 'petition', hoping to receive
> > information/update on the Android SDK.
> > (+1) plusminus
> > Regards, plusminus
> >http://anddev.org > > # Worlds largest Android Development Community / Tutorials
> > PS: I didn't want to depreciate the work of the Android Dev Team or
> > anyone else.
BTW, i'm not really tied to only Android platform. iPhone, Windows Mobile, Symbian, OpenMoko are all viable choices. As for mobile development, it's never a good direction to only develop for one specific platform, unless it's for a specific reason :)
I'm afraid (at the same time excited) that by the time the next Android SDK is released (close to EOY 2008 I guess), many developers here have already released software on the iPhone platform, a platform with 20+ million users versus ZERO user install base for Android. It's not a hard decision to make after all. Hopefully someone wakes up sooner than later.
(+1)
I am holding out hope for Android but my development efforts are
currently focused elsewhere and will be until Google makes some
significant positive moves.
On Jun 28, 6:57 pm, plusminus <stoeps...@gmx.de> wrote:
> I'm starting this petition, to express my personal frustration about
> the release cycles and the information policy of the Android SDK.
> Before m5 we were waiting about 2 months, now we are waiting almost 4
> months!
> Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its
> time to release some news about the development process of the SDK.
> Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a
> lot of work into the community through my forum. But unfortunately
> disappointment is being born in the last weeks :(
> (Especially thinking of recently existing OpenMoko-Phones and the new
> iPhone SDK).
> In my personal opinion it is not the right choice to keep developers
> in the dark. We, the developers, are the absolute base of success to
> the whole Android platform. The presentation with GoogleIO was a good
> first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive
> information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or
> anyone else.
(+-),... (+1)
... I'm hoping they are building and umbilical cord to an agent
running web entity for each phone. That is, of course, the obvious
way to do it but not necessarily the easiest. I am presuming that
they are doing work that I want to build off of and would rather have
them do. Google has hired each of their employees stating that they
are a 'dog company.' If they get catty with Android developers they
violate employee contracts with each and every one of their employees.
A part of the benefits of working for a particular employer is the
good will bestowed by the population at large on people serving
community by working for that employer. If they are now greeted by
cold stares and shuttered doorways whenever they walk into a room for
the way they have treated the android development community, then that
real benefit is gone.
The other companies in the OHA (...no way are They going to make an
open foot phone!) are not bound by that contractual obligation.
Google needs to make it a bit more clear to their partners that they
have a prior contractual obligation to each and every employee to
treat the android development community right.
Trusting that Google is still a dog company and they will honor the
contracts made with employees at time of hire, I think they are
working to make the wait on the SDK worth it.
Folks here are doing their part in good faith. I'm making a
significant public communication effort to head off frivolous patents
so folks can work unfettered to serve ordinary people. I am also
writing code at the algorithm/UI level to do what needs to be done,
leaving the interface work for Google in their next SDK, or for people
with existing dexterity there.
As long as Google is making prior contractual obligations clear to
their new partners,...
I will sign the petition to be an audience for Google as they show a
little backbone.
On Jun 28, 4:57 am, plusminus <stoeps...@gmx.de> wrote:
> I'm starting this petition, to express my personal frustration about
> the release cycles and the information policy of the Android SDK.
> Before m5 we were waiting about 2 months, now we are waiting almost 4
> months!
> Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its
> time to release some news about the development process of the SDK.
> Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a
> lot of work into the community through my forum. But unfortunately
> disappointment is being born in the last weeks :(
> (Especially thinking of recently existing OpenMoko-Phones and the new
> iPhone SDK).
> In my personal opinion it is not the right choice to keep developers
> in the dark. We, the developers, are the absolute base of success to
> the whole Android platform. The presentation with GoogleIO was a good
> first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive
> information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or
> anyone else.
I believe many developers are losing interest in Android after ADC I.
I am currently having a good time developing applications for the
iPhone
and iPod Touch.
Android is still a superior platform but lack of update from Google
really
makes many of the developers feeling extremely frustrated.
On Jun 28, 2:57 am, plusminus <stoeps...@gmx.de> wrote:
> I'm starting this petition, to express my personal frustration about
> the release cycles and the information policy of the Android SDK.
> Before m5 we were waiting about 2 months, now we are waiting almost 4
> months!
> Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its
> time to release some news about the development process of the SDK.
> Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a
> lot of work into the community through my forum. But unfortunately
> disappointment is being born in the last weeks :(
> (Especially thinking of recently existing OpenMoko-Phones and the new
> iPhone SDK).
> In my personal opinion it is not the right choice to keep developers
> in the dark. We, the developers, are the absolute base of success to
> the whole Android platform. The presentation with GoogleIO was a good
> first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive
> information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or
> anyone else.
+1 I am not a developer but I have been keeping track of this and have seen that it is causing some major problems for the developers which could kill Android and I really do not want to see that happen.
+1 Would like to see from winners if they support this call too?
I don't understand at times Google's way of thinking.
- Google has announced the Android platform. - Then Google restricts access to a community that is there for this potentially wonderful open platform to sustain its growth. - that itself(big G) doesn't seem like internally you have what it takes to sustain this platform due to slow releases & updates, when the community is at its doorstep!!
*knock, knock!!*
truly hope this wont be anything like ADC 1, that IMHO was a disaster!
+1, though I think there's gotta be one coming soon...I don't have any inside information, just seems like there is no reason they wouldn't be working on getting a new public sdk out.
--
Zach Hobbs HelloAndroid.com Android OS news, tutorials, downloads
On Saturday 28 June 2008 05:57:44 plusminus wrote:
> I'm starting this petition, to express my personal frustration about > the release cycles and the information policy of the Android SDK. > Before m5 we were waiting about 2 months, now we are waiting almost 4 > months! > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like > built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its > time to release some news about the development process of the SDK. > Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a > lot of work into the community through my forum. But unfortunately > disappointment is being born in the last weeks :( > (Especially thinking of recently existing OpenMoko-Phones and the new > iPhone SDK).
> In my personal opinion it is not the right choice to keep developers > in the dark. We, the developers, are the absolute base of success to > the whole Android platform. The presentation with GoogleIO was a good > first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive > information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminus > http://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or > anyone else.
it's weird the way that google is coming into this mobile marketing and mobile computing world... I think that how can I develop on a platform that hasnt even a cell phone implementing and they're launching lots of upgrades and newer sdk's??? Im not an emulator programmer! i'd rather to be investing on some other concrete platforms and just be apart of what is going on with these kind of promises like "android"...
On Sun, Jun 29, 2008 at 5:32 PM, Zach Hobbs <ho...@helloandroid.com> wrote:
> +1, though I think there's gotta be one coming soon...I don't have any > inside > information, just seems like there is no reason they wouldn't be working on > getting a new public sdk out.
> On Saturday 28 June 2008 05:57:44 plusminus wrote: > > Hello everyone,
> > I'm starting this petition, to express my personal frustration about > > the release cycles and the information policy of the Android SDK. > > Before m5 we were waiting about 2 months, now we are waiting almost 4 > > months! > > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like > > built-in Geocoding are not working.
> > In order not to lose many highly encouraged developers, I think its > > time to release some news about the development process of the SDK. > > Maybe let us know why we have to live with these long cycles.
> > As you maybe know, I am one of the biggest fans of Android, putting a > > lot of work into the community through my forum. But unfortunately > > disappointment is being born in the last weeks :( > > (Especially thinking of recently existing OpenMoko-Phones and the new > > iPhone SDK).
> > In my personal opinion it is not the right choice to keep developers > > in the dark. We, the developers, are the absolute base of success to > > the whole Android platform. The presentation with GoogleIO was a good > > first step but for me it was nto enough.
> > Therefore I am 'signing' this 'petition', hoping to receive > > information/update on the Android SDK.
> > (+1) plusminus
> > Regards, plusminus > > http://anddev.org > > # Worlds largest Android Development Community / Tutorials
> > PS: I didn't want to depreciate the work of the Android Dev Team or > > anyone else.
> +1, though I think there's gotta be one coming soon...I don't have any inside
> information, just seems like there is no reason they wouldn't be working on
> getting a new public sdk out.
> On Saturday 28 June 2008 05:57:44 plusminus wrote:
> > Hello everyone,
> > I'm starting this petition, to express my personal frustration about
> > the release cycles and the information policy of the Android SDK.
> > Before m5 we were waiting about 2 months, now we are waiting almost 4
> > months!
> > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> > built-in Geocoding are not working.
> > In order not to lose many highly encouraged developers, I think its
> > time to release some news about the development process of the SDK.
> > Maybe let us know why we have to live with these long cycles.
> > As you maybe know, I am one of the biggest fans of Android, putting a
> > lot of work into the community through my forum. But unfortunately
> > disappointment is being born in the last weeks :(
> > (Especially thinking of recently existing OpenMoko-Phones and the new
> > iPhone SDK).
> > In my personal opinion it is not the right choice to keep developers
> > in the dark. We, the developers, are the absolute base of success to
> > the whole Android platform. The presentation with GoogleIO was a good
> > first step but for me it was nto enough.
> > Therefore I am 'signing' this 'petition', hoping to receive
> > information/update on the Android SDK.
> > (+1) plusminus
> > Regards, plusminus
> >http://anddev.org > > # Worlds largest Android Development Community / Tutorials
> > PS: I didn't want to depreciate the work of the Android Dev Team or
> > anyone else.
> I'm starting this petition, to express my personal frustration about
> the release cycles and the information policy of the Android SDK.
> Before m5 we were waiting about 2 months, now we are waiting almost 4
> months!
> Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its
> time to release some news about the development process of the SDK.
> Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a
> lot of work into the community through my forum. But unfortunately
> disappointment is being born in the last weeks :(
> (Especially thinking of recently existing OpenMoko-Phones and the new
> iPhone SDK).
> In my personal opinion it is not the right choice to keep developers
> in the dark. We, the developers, are the absolute base of success to
> the whole Android platform. The presentation with GoogleIO was a good
> first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive
> information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or
> anyone else.
Here is one of the broken ASDK pieces that i am looking forward for
"more precisely glue".
When both ddms and emulator are running on the same host, how can this
happen?????? There are obviously either timing issue or other
misdesign in some ASDK component.
> +1, though I think there's gotta be one coming soon...I don't have any inside
> information, just seems like there is no reason they wouldn't be working on
> getting a new public sdk out.
> On Saturday 28 June 2008 05:57:44 plusminus wrote:
> > Hello everyone,
> > I'm starting this petition, to express my personal frustration about
> > the release cycles and the information policy of the Android SDK.
> > Before m5 we were waiting about 2 months, now we are waiting almost 4
> > months!
> > Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> > built-in Geocoding are not working.
> > In order not to lose many highly encouraged developers, I think its
> > time to release some news about the development process of the SDK.
> > Maybe let us know why we have to live with these long cycles.
> > As you maybe know, I am one of the biggest fans of Android, putting a
> > lot of work into the community through my forum. But unfortunately
> > disappointment is being born in the last weeks :(
> > (Especially thinking of recently existing OpenMoko-Phones and the new
> > iPhone SDK).
> > In my personal opinion it is not the right choice to keep developers
> > in the dark. We, the developers, are the absolute base of success to
> > the whole Android platform. The presentation with GoogleIO was a good
> > first step but for me it was nto enough.
> > Therefore I am 'signing' this 'petition', hoping to receive
> > information/update on the Android SDK.
> > (+1) plusminus
> > Regards, plusminus
> >http://anddev.org > > # Worlds largest Android Development Community / Tutorials
> > PS: I didn't want to depreciate the work of the Android Dev Team or
> > anyone else.
this SDK is so buggy that we desperately need an update
BTW ... will there be any multi-touch support ?
Multi-touch might be hard to emulate but is way more cooler to have
pinching and starching as events.
> this SDK is so buggy that we desperately need an update
> BTW ... will there be any multi-touch support ?
> Multi-touch might be hard to emulate but is way more cooler to have
> pinching and starching as events.
> > this SDK is so buggy that we desperately need an update > > BTW ... will there be any multi-touch support ? > > Multi-touch might be hard to emulate but is way more cooler to have > > pinching and starching as events.
> > regards
-- Sun Certified Programmer for Java Platform, SE 5.0 – 310-055.
+1
I haven't had such a rough experience on the technical side and
reached the level of full app's end-to-end months ago. We've all built
our stuff at risk, but I have had it for now.
I am not keen to find out I've painted myself into a corner over the
summer when an SDK update finally comes out. I guess I'll hang out at
the beach more. Summer of no code...
JP
On Jul 1, 11:16 pm, "gunaz...@gmail.com" <gunaz...@gmail.com> wrote:
> I'm starting this petition, to express my personal frustration about
> the release cycles and the information policy of the Android SDK.
> Before m5 we were waiting about 2 months, now we are waiting almost 4
> months!
> Partially the SDK is buggy (i.e.: the MediaPlayer) and features like
> built-in Geocoding are not working.
> In order not to lose many highly encouraged developers, I think its
> time to release some news about the development process of the SDK.
> Maybe let us know why we have to live with these long cycles.
> As you maybe know, I am one of the biggest fans of Android, putting a
> lot of work into the community through my forum. But unfortunately
> disappointment is being born in the last weeks :(
> (Especially thinking of recently existing OpenMoko-Phones and the new
> iPhone SDK).
> In my personal opinion it is not the right choice to keep developers
> in the dark. We, the developers, are the absolute base of success to
> the whole Android platform. The presentation with GoogleIO was a good
> first step but for me it was nto enough.
> Therefore I am 'signing' this 'petition', hoping to receive
> information/update on the Android SDK.
> (+1) plusminus
> Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials
> PS: I didn't want to depreciate the work of the Android Dev Team or
> anyone else.
i lost patience long ago. will keep coding/waiting untill the end of
july. then ill eigther switch to the iphone (if sells are good) or
windows mobile. i see absolutely no use in working with a barely
finished SDK on an emulator without a piece of hardware in my hand.
MOBILE phone development is no fun if you cant test it MOBILE.
just-some-guy: is this a way of saying that we (Google Android team)
should continue to focus on making sure that devices can be available
as quickly as we possibly can?
JBQ (Android Engineer).
On Jul 11, 1:42 am, just-some-guy <google-analytics....@daloo.de>
wrote:
> i lost patience long ago. will keep coding/waiting untill the end of
> july. then ill eigther switch to the iphone (if sells are good) or
> windows mobile. i see absolutely no use in working with a barely
> finished SDK on an emulator without a piece of hardware in my hand.
> MOBILE phone development is no fun if you cant test it MOBILE.
