Petition - Information about upcoming SDKs!
65 views
Skip to first unread message
plusminus
Jun 28, 2008, 5:57:44 AM6/28/08
to Android Discuss
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, 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.
Muthu Ramadoss
Jun 28, 2008, 10:01:14 AM6/28/08
to android...@googlegroups.com
+1 for a public SDK release.--
take care,
Muthu Ramadoss.
http://cookingcapsules.com - nourish your droid.
http://mobeegal.in - find stuff closer.
take care,
Muthu Ramadoss.
http://cookingcapsules.com - nourish your droid.
http://mobeegal.in - find stuff closer.
Shane Isbell
Jun 28, 2008, 10:07:35 AM6/28/08
to Android Discuss
+1
> http://cookingcapsules.com- nourish your droid.http://mobeegal.in- find stuff closer.- Hide quoted text -
>
> - Show quoted text -
>
> - Show quoted text -
Hong
Jun 28, 2008, 1:30:42 PM6/28/08
to android...@googlegroups.com
+1
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.
HOng
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.
HOng
hitsu_g
Jun 28, 2008, 7:13:29 AM6/28/08
to Android Discuss
(+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:
> 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, plusminushttp://anddev.org
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:
> 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
>
efon...@gmail.com
Jun 28, 2008, 4:36:43 PM6/28/08
to Android Discuss
(+-),... (+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:
> 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, plusminushttp://anddev.org
... 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:
> 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
>
j
Jun 29, 2008, 12:37:35 AM6/29/08
to Android Discuss
(+1)
jalopy
Jun 29, 2008, 3:32:52 AM6/29/08
to Android Discuss
( +1 )
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:
> 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, plusminushttp://anddev.org
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:
> 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
>
thex...@netzero.net
Jun 29, 2008, 3:54:55 AM6/29/08
to android...@googlegroups.com
+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.
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.
____________________________________________________________
Recharge and relax. Click for great vacation ideas.
http://thirdpartyoffers.netzero.net/TGL2241/fc/Ioyw6i4uHYu6EyayYhI7l7h7uFXo5ZRVevPKDAuw3viHqoWiZ3GVad/
fred lin
Jun 29, 2008, 8:10:37 AM6/29/08
to Android Discuss
+1
--
fred
--
fred
george_c
Jun 29, 2008, 1:43:03 PM6/29/08
to android...@googlegroups.com
+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!
George
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!
George
Zach Hobbs
Jun 29, 2008, 4:32:12 PM6/29/08
to android...@googlegroups.com
+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.
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
Lucas Abrão
Jun 29, 2008, 9:59:04 PM6/29/08
to android...@googlegroups.com
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"...
Nickname
Jun 29, 2008, 7:52:56 PM6/29/08
to Android Discuss
+1
Looking forward to a less-frustrating SDK with more precisely glued
Eclipse-Emulator interaction!!!!!!!!!!!!!!!!!!!!!!!!!!!
Looking forward to a less-frustrating SDK with more precisely glued
Eclipse-Emulator interaction!!!!!!!!!!!!!!!!!!!!!!!!!!!
Randy Power
Jun 29, 2008, 10:12:44 PM6/29/08
to Android Discuss
+1 I appreciate the Android Dev Team, but am losing some Android
steam.
On Jun 28, 4:57 am, 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, plusminushttp://anddev.org
steam.
On Jun 28, 4:57 am, 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
>
Luc1an
Jun 29, 2008, 5:48:00 PM6/29/08
to Android Discuss
Nickname
Jun 29, 2008, 9:28:20 PM6/29/08
to Android Discuss
+1,
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.
[2008-06-29 18:22:58 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:03 - ddms] execute: running ls -l /
[2008-06-29 18:23:03 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:08 - ddms] execute: running ls -l /
[2008-06-29 18:23:08 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:13 - ddms] execute: running ls -l /
[2008-06-29 18:23:13 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:18 - ddms] execute: running ls -l /
[2008-06-29 18:23:18 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:23 - ddms] execute: running ls -l /
[2008-06-29 18:23:23 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:28 - ddms] execute: running ls -l /
[2008-06-29 18:23:28 - ddms] Got reply 'FAIL', diag='no device'
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.
[2008-06-29 18:22:58 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:03 - ddms] execute: running ls -l /
[2008-06-29 18:23:03 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:08 - ddms] execute: running ls -l /
[2008-06-29 18:23:08 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:13 - ddms] execute: running ls -l /
[2008-06-29 18:23:13 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:18 - ddms] execute: running ls -l /
[2008-06-29 18:23:18 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:23 - ddms] execute: running ls -l /
[2008-06-29 18:23:23 - ddms] Got reply 'FAIL', diag='no device'
[2008-06-29 18:23:28 - ddms] execute: running ls -l /
[2008-06-29 18:23:28 - ddms] Got reply 'FAIL', diag='no device'
pmilosev
Jun 30, 2008, 3:34:41 AM6/30/08
to Android Discuss
+ inf
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
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
rezar
Jul 1, 2008, 9:14:10 AM7/1/08
to Android Discuss
+2
Thomas Modeneis
Jul 1, 2008, 9:20:57 AM7/1/08
to android...@googlegroups.com
+1--
Sun Certified Programmer for Java Platform, SE 5.0 – 310-055.
Sun Certified Programmer for Java Platform, SE 5.0 – 310-055.
guna...@gmail.com
Jul 2, 2008, 2:16:17 AM7/2/08
to Android Discuss
+1..
Wants new sdk without bugs as soon as possible...
Many functionalities missing and many mock class only available..
Regards,
Guna.
Wants new sdk without bugs as soon as possible...
Many functionalities missing and many mock class only available..
Regards,
Guna.
JP
Jul 2, 2008, 10:12:20 AM7/2/08
to Android Discuss
+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
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
Andrew Lewis
Jul 3, 2008, 5:38:44 PM7/3/08
to Android Discuss
+1 for a roadmap of future SDK releases
On Jun 28, 3:57 am, 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, plusminushttp://anddev.org
On Jun 28, 3:57 am, 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
>
just-some-guy
Jul 11, 2008, 4:42:25 AM7/11/08
to Android Discuss
(+1)
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.
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.
JBQ
Jul 11, 2008, 12:16:16 PM7/11/08
to Android Discuss
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:
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:
JP
Jul 11, 2008, 2:28:55 PM7/11/08
to Android Discuss
It is a way of saying not to cut off the community at large. It has
not been received well that SDK updates are available to only few
under NDA, selected by the Challenge, without letting anybody know.
This could have been explained and accepted without much fuss.
An hour per day worth of effort (my estimate) is all it would take to
keep the community informed - and even if things cannot be shared with
the public at a certain point, the bare minimum that we (the developer
community) could reasonably expect is to at least be kept in the loop
on the superficial level.
Right now the developer community seems to fall apart. This post-
Challenge period left an impression with many that we're considered
Google roadkill. All the way through spring this year we accepted to
build our apps at-risk (no established platform). Fine, but we did not
expect getting dropped like a hot potato. This has pushed me over
anyways. Summer of no code here.
It's a bummer really - a browse through Apple's brand new app store
leaves me largely unimpressed.
JP
> > MOBILE phone development is no fun if you cant test it MOBILE.- Hide quoted text -
not been received well that SDK updates are available to only few
under NDA, selected by the Challenge, without letting anybody know.
This could have been explained and accepted without much fuss.
An hour per day worth of effort (my estimate) is all it would take to
keep the community informed - and even if things cannot be shared with
the public at a certain point, the bare minimum that we (the developer
community) could reasonably expect is to at least be kept in the loop
on the superficial level.
Right now the developer community seems to fall apart. This post-
Challenge period left an impression with many that we're considered
Google roadkill. All the way through spring this year we accepted to
build our apps at-risk (no established platform). Fine, but we did not
expect getting dropped like a hot potato. This has pushed me over
anyways. Summer of no code here.
It's a bummer really - a browse through Apple's brand new app store
leaves me largely unimpressed.
JP
efon...@gmail.com
Jul 11, 2008, 11:34:20 PM7/11/08
to Android Discuss
Isn't it Google policy that you learn stuff by getting it in people's
hands as quickly as possible?
This developer's concern is that in the rush Google makes a bad deal
with the carrier that results in an undifferentiated product (with
little access to network location information and a cumbersome
connection to the cloud).
Dear Google Android Team,
Please act in a way that supports the business folks in their
negotiations with carriers to get a differentiated product to
customers. A product that allows ordinary people to bring new network
and location benefits to other ordinary people.
hands as quickly as possible?
This developer's concern is that in the rush Google makes a bad deal
with the carrier that results in an undifferentiated product (with
little access to network location information and a cumbersome
connection to the cloud).
Dear Google Android Team,
Please act in a way that supports the business folks in their
negotiations with carriers to get a differentiated product to
customers. A product that allows ordinary people to bring new network
and location benefits to other ordinary people.
JP
Jul 12, 2008, 12:43:40 AM7/12/08
to Android Discuss
On Jul 11, 8:34 pm, "efont...@gmail.com" <efont...@gmail.com> wrote:
> that in the rush Google makes a bad deal
> with the carrier that results in an undifferentiated product (with
Exactly my concern, too. Like reading my mind. Before adding to this
however I'd like to say thanks to JBQ for checking in.
Back on top topic though; if carriers create derivate work from
Android to brand their devices, it's still going to be an Android
phone, right? And at least under the current license there's nothing
that Google can do to prevent this from happening. Let's have a look
at the tools that hang up there at the torture chamber wall. What
third-party apps might be denied of; what comes to mind within 10
seconds:
- access to contacts, messaging and phone controls
- location device (GPS) access
- maps through MapView (hope the TeleAtlas deal will prevent that (but
again we're hoping here))
Now why's that? Easy answer - all it takes is Wayfinder to come in,
ink an exclusive deal with carrier, charge the usual $129 and kick
back part of the revenue to the carrier. Independent developer: Out.
Consumers care? Unlikely, in particular here in the US; unless perhaps
there's a change in attitudes given the current economic downturn with
people looking for actual value products when they shell out hundreds
of dollars... unlikely though.
So there's an awful lot of things that can go wrong and it doesn't
even cover the usual annoyances like SIM locks, tethering locks (see
iPhone 3G) etc.
So we won't know *anything* until later this year, it seems? That's
why communications are so important.
JBQ
Jul 12, 2008, 9:59:22 AM7/12/08
to Android Discuss
I'm going to get into trouble for this post...
I was a bit facetious in my previous post, I'm sorry about that, I
shouldn't have been playing with people's feelings like that, that was
somewhat inappropriate.
There is some truth however in saying that we (the Google Android
team) are very much focusing on playing our part in getting an Android
device on the shelves as soon as we possibly can, and that focus comes
at the expense of other tasks, like getting an SDK out. Since I'm
talking about that, I'll also point out that there's a large lag
between delivery of the final software to a manufacturer and
commercial availability of device with that software: there's a phase
of approvals, acceptance and certification, followed by manufacturing,
shipping and distribution, which take a fair amount of time. That
period of time is quite suitable for tasks like getting an SDK ready.
I've been personally involved in shipping cell phone software for
years, in a way that included an SDK, and invariably we'd build the
SDK after the final embedded software was released (so that we could
get as close a match as possible) and yet the SDK would be ready well
in advance of the availability of devices.
There've been quite a few long threads recently in various groups
(this thread, along with one in android-developers and one in android-
internals) around the issue of communication from Google. I'm sure
that many of the people who participated in those threads get the
feeling that their comments fell on deaf ears, whereas in fact that's
not true. Quite a few members of the Google Android team read those
groups (and we also read a number of community web sites), and (quite
a bit by definition) we are the ones who do care about the community.
Many of us have played roles in various developer communities in the
past, very often on both sides of the fence, and in more ways that one
we understand the situation that the developer community is in right
now and we share the pain. So, while those posts aren't falling on
deaf ears, they're typically falling in the wide-open ears of people
whose hands are tied and whose mouths are gagged, and the frustration
that such posts create in the Android team might in fact be larger
than the relief that gets created in the community.
I will say however, from personal experience being a third-party
developer for a certain platform before it shipped to customers, and
having gone through 5 major "developer" releases and 2 "preview"
releases of that platform, that getting many releases of a framework
that is undergoing active development before its first release is a
frustrating experience in itself. I remember investing a lot of energy
writing code around a certain feature that appeared in one of the
developer releases, only to see that feature disappear in a later
release. And of course that says nothing about the frustration of
porting my code from one release to the next in order to benefit from
certain bug fixes, only to find after a lot of porting effort that
bugs introduced in the newer release got in my ways more than the ones
I had ran into in the previous release. Looking back, I wish that I
had focused more on my system's architecture and on the core of my
code (which were the valuable parts), and less on chasing one SDK
after the other.
Back to the question, and to keep things simple, we've announced that
"the entire platform will be made available under the very liberal,
developer-friendly Apache v2 open-source license" (sorry I had to
quote that, I really have to be very careful about what I say here).
As I understand (but I am not a lawyer), the Apache License, Version
2.0 grants certain rights related to copyright and patents, but
explicitly does not grant permissions in the trademark area. So, there
is some openness about what people will be allowed to do with the
platform as it gets released, but not necessary about how they can
call the result. Once again, I am not a lawyer, and that is obviously
not legal advice.
Ultimately, the market forces will prevail. This is a complex
ecosystem, though, with consumers, network operators, and third-party
developers playing a role (and I'm not even putting software providers
and device manufacturers in the list). The way I see it, if there are
enough excellent third-party applications, consumers will be willing
to pay more money for devices that can run those applications, and
network operators will have an incentive to allow those applications
to run. I said earlier that I'm not a lawyer, and I'll say here that
I'm not an economist either, and what I just wrote about the market it
very primitive and probably very naive too.
I'm afraid that none of all that I just wrote brings any closure in
terms of communication. That's all because it's not my role to
communicate the "big picture" answers that people would like to hear.
The Google Android people who read the groups hear you, we understand
your pain, we communicate it back up to our management, we're not
happy about the situation either, we'd love more openness too. And,
just like anybody else, we don't like to read implications that we're
lazy, or that we're liars, or that we don't care about you, or any of
the other nasty things that have been written or implied about us,
because none of that it true.
JBQ (Android Engineer)
I was a bit facetious in my previous post, I'm sorry about that, I
shouldn't have been playing with people's feelings like that, that was
somewhat inappropriate.
There is some truth however in saying that we (the Google Android
team) are very much focusing on playing our part in getting an Android
device on the shelves as soon as we possibly can, and that focus comes
at the expense of other tasks, like getting an SDK out. Since I'm
talking about that, I'll also point out that there's a large lag
between delivery of the final software to a manufacturer and
commercial availability of device with that software: there's a phase
of approvals, acceptance and certification, followed by manufacturing,
shipping and distribution, which take a fair amount of time. That
period of time is quite suitable for tasks like getting an SDK ready.
I've been personally involved in shipping cell phone software for
years, in a way that included an SDK, and invariably we'd build the
SDK after the final embedded software was released (so that we could
get as close a match as possible) and yet the SDK would be ready well
in advance of the availability of devices.
There've been quite a few long threads recently in various groups
(this thread, along with one in android-developers and one in android-
internals) around the issue of communication from Google. I'm sure
that many of the people who participated in those threads get the
feeling that their comments fell on deaf ears, whereas in fact that's
not true. Quite a few members of the Google Android team read those
groups (and we also read a number of community web sites), and (quite
a bit by definition) we are the ones who do care about the community.
Many of us have played roles in various developer communities in the
past, very often on both sides of the fence, and in more ways that one
we understand the situation that the developer community is in right
now and we share the pain. So, while those posts aren't falling on
deaf ears, they're typically falling in the wide-open ears of people
whose hands are tied and whose mouths are gagged, and the frustration
that such posts create in the Android team might in fact be larger
than the relief that gets created in the community.
I will say however, from personal experience being a third-party
developer for a certain platform before it shipped to customers, and
having gone through 5 major "developer" releases and 2 "preview"
releases of that platform, that getting many releases of a framework
that is undergoing active development before its first release is a
frustrating experience in itself. I remember investing a lot of energy
writing code around a certain feature that appeared in one of the
developer releases, only to see that feature disappear in a later
release. And of course that says nothing about the frustration of
porting my code from one release to the next in order to benefit from
certain bug fixes, only to find after a lot of porting effort that
bugs introduced in the newer release got in my ways more than the ones
I had ran into in the previous release. Looking back, I wish that I
had focused more on my system's architecture and on the core of my
code (which were the valuable parts), and less on chasing one SDK
after the other.
Back to the question, and to keep things simple, we've announced that
"the entire platform will be made available under the very liberal,
developer-friendly Apache v2 open-source license" (sorry I had to
quote that, I really have to be very careful about what I say here).
As I understand (but I am not a lawyer), the Apache License, Version
2.0 grants certain rights related to copyright and patents, but
explicitly does not grant permissions in the trademark area. So, there
is some openness about what people will be allowed to do with the
platform as it gets released, but not necessary about how they can
call the result. Once again, I am not a lawyer, and that is obviously
not legal advice.
Ultimately, the market forces will prevail. This is a complex
ecosystem, though, with consumers, network operators, and third-party
developers playing a role (and I'm not even putting software providers
and device manufacturers in the list). The way I see it, if there are
enough excellent third-party applications, consumers will be willing
to pay more money for devices that can run those applications, and
network operators will have an incentive to allow those applications
to run. I said earlier that I'm not a lawyer, and I'll say here that
I'm not an economist either, and what I just wrote about the market it
very primitive and probably very naive too.
I'm afraid that none of all that I just wrote brings any closure in
terms of communication. That's all because it's not my role to
communicate the "big picture" answers that people would like to hear.
The Google Android people who read the groups hear you, we understand
your pain, we communicate it back up to our management, we're not
happy about the situation either, we'd love more openness too. And,
just like anybody else, we don't like to read implications that we're
lazy, or that we're liars, or that we don't care about you, or any of
the other nasty things that have been written or implied about us,
because none of that it true.
JBQ (Android Engineer)
Muthu Ramadoss
Jul 12, 2008, 10:26:05 AM7/12/08
to android...@googlegroups.com
JBQ,
We hear you. Thanks for taking your time and communicating with the android developer community. This I hope is the first step in bridging the gap that was created between Google and the Android development community after the public SDK stopped coming.
Hats off. Keep posting.
Thanks.--
take care,
Muthu Ramadoss.
http://cookingcapsules.com - nourish your droid.
http://mobeegal.in - find stuff closer.
We hear you. Thanks for taking your time and communicating with the android developer community. This I hope is the first step in bridging the gap that was created between Google and the Android development community after the public SDK stopped coming.
Hats off. Keep posting.
Thanks.
take care,
Muthu Ramadoss.
http://cookingcapsules.com - nourish your droid.
http://mobeegal.in - find stuff closer.
Mark Murphy
Jul 12, 2008, 11:47:05 AM7/12/08
to android...@googlegroups.com
First, I'd like to echo Muthu's sentiments -- many thanks on making this
post!
post!
JBQ wrote:
> So, while those posts aren't falling on
> deaf ears, they're typically falling in the wide-open ears of people
> whose hands are tied and whose mouths are gagged, and the frustration
> that such posts create in the Android team might in fact be larger
> than the relief that gets created in the community.
You probably can't answer this, but...
Is there anything we can do to assist with untying the hands and/or
un-gagging the mouths? Besides being patient, of course.
<voice tone="conspiratorial">
(and if you can't speak freely, cough twice in your response)
</voice>
;-)
> And,
> just like anybody else, we don't like to read implications that we're
> lazy, or that we're liars, or that we don't care about you, or any of
> the other nasty things that have been written or implied about us,
> because none of that it true.
I can't speak for those who have been more...vociferous in their
ranting, but I doubt that many of the shouts have truly been directed at
engineers. I think they have been more aimed at the "project", which, at
present, is a black box (e.g., where does Google end and OHA begin?).
Again, not speaking for anyone else, I apologize if the Android
engineering team feels persecuted due to the communications lockdown and
our reaction to same.
In many ways, we only rant because we care... :-)
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android Training on the Ranch in September! http://www.bignerdranch.com
JP
Jul 12, 2008, 12:18:19 PM7/12/08
to Android Discuss
On Jul 12, 7:26 am, "Muthu Ramadoss" <muthu.ramad...@gmail.com> wrote:
> JBQ,
>
> We hear you. Thanks for taking your time and communicating with the android
> developer community. This I hope is the first step in bridging the gap that
> was created between Google and the Android development community after the
> public SDK stopped coming.
>
> Hats off. Keep posting.
>
> Thanks.
It's not like we could (seriously) expect answers to big picture
question. The Android team cannot control some considerable aspects in
the first place. But at least keep the channels open about the aspects
you can. And if for one reason or another, some things cannot be
shared at one point, it's perfectly fine to state that that's the case
and if possible explain that.
Like we've seen there's a pretty bad impact when you cut off. I am
miffed for example (to inject a grief I've had recently) that the 1800-
number (number of entries to the Challenge I) is leveraged in the
press when on the other side we see treatment like we have. Guy's....
don't do stuff like that, especially considering that you'll need all
hands on deck when you need leverage to fight for *your* (and ours:
open source) interest when things are getting tight; and they will.
When someone ends up with bad compromises, at least one can go to
sleep at night and tell him or herself: you've done everything
possible.
I've been sloppy working out that Android licensing thought. What I
probably should have said was that carriers will likely go out and
(evil-)brand their product/service based on an Android derivative,
call it whatever their legal advisers will endorse, what they can
train their marketeers to pitch and what will provide maximum leverage
of the Google brand name (in the bigger picture: does the "Android"
name mean much anyhow). If things play out that way... *that's* going
to be pain for the Android team and it has been a bit of a shocker to
see how you guys cut off communications on a relatively easy set of
stakeholders like us. You all's have credit 'round here, but
immediately it raises doubt whether you are prepared to fight a fight
with the carriers when the Android team can't get the seemingly simple
things done.
Let me also say that one of the darker side aspects to me is
unceremoniously cutting off the developer advocates. Unless I've
gotten the wrong impression: This has torched Dan M. and others who
have been busting their tails off just a few months ago. A good time
to recognize their efforts, now that we know (not just suspect) that
they've been gagged. Seriously I hope they're not getting a heart
attack; there's been a bunch including myself who have been turning on
the heat...
For my personal entertainment I'll say I suppose they did not expect
something like this to happen when they walked by expecting mother
parking signs on their way to their first job interview. (;->)
Re: chasing SDK's: It's about what poison to chose. There's no right
answer. If we can't get visibility where the SDK goes, the concerns
with every piece of code we implement and every design decision we
take on an "old" release is that we might paint ourselves into a
corner. Lessons learned about focusing on design and architecture are
all valuable, but in the end it's code that actually runs on a
platform, not concepts, and that's what keeps us (or at least me)
going.
JP
Jul 12, 2008, 12:21:18 PM7/12/08
to Android Discuss
On Jul 12, 8:47 am, Mark Murphy <mmur...@commonsware.com> wrote:
> I can't speak for those who have been more...vociferous in their
> ranting, but I doubt that many of the shouts have truly been directed at
> engineers. I think they have been more aimed at the "project", which, at
> present, is a black box (e.g., where does Google end and OHA begin?).
> Again, not speaking for anyone else, I apologize if the Android
> engineering team feels persecuted due to the communications lockdown and
> our reaction to same.
>
> In many ways, we only rant because we care... :-)
Hong
Jul 11, 2008, 12:23:24 PM7/11/08
to android...@googlegroups.com
JBQ, we need an updated SDK. That's the original point of this post.
Why dodge the main concern us developers are having now?
Why dodge the main concern us developers are having now?
Shane Isbell
Jul 11, 2008, 12:52:34 PM7/11/08
to android...@googlegroups.com
I think we are all aware by now that Google doesn't have the resources to cut an SDK release, doing a community focus, AND to get the devices launched. This is perfectly understandable; it seems to me that a lot of developers are merely saying that it is no longer their problem.
Shane