Wall Street Journal article today - are things going down the drain for independent developers?

by JP » Tue, 24 Jun 2008 02:01:31 GMT


Sponsored Links
 The WSJ has an article today about the state of the affairs in the
Android empire.
 http://online.wsj.com/public/article/SB121418837707895947.html?mod=2_1571_leftbox 
Looks like the journalists made a number of phone calls and did not
just regurgitate some blogs - some solid insights into carriers and
developers' current situation, it seems. I have the following
takeaways from the article:
- For app developers, there is a world of two speeds. If you got "in"
through the Challenge or some other relationship, you already have
access to information about the next SDK, draft release notes at the
minimum, probably the SDK itself. Nothing in sight to the public
though. Or did I miss something? The WeatherChannel developer anyways
indirectly confirms this, which means they are getting a headstart to
implement the necessary changes to their apps, while everybody else
has to sit and wait.
- Carriers are busy branding "their" Android. Worst case, we can
expect subsidized-only phones a la iPhone, which only include apps
which made it on the inside track, while independent developers cannot
load and test theirs (superficial carrier explanation here: copy Steve
Jobs excuses of yore). The first batches of Android phones will
certainly come with aggressive SIM locks - no question in my mind, but
I might be proven wrong.
It'll be interesting to see however if enthusiasts can flash these
suckers from clean Android images without too much trouble. Sans SIM
lock, sans branding, but I suspect special service cables will be
needed which are not available to the public. Needless to say that
we'll be told we'll burn in hell (or worse) if we choose to pursue
this.

Overall... question marks keep piling up for independent developers.
Looks like we are getting squeezed out of the race to market? Perhaps
some clarifying words by the developer advocates at Google might give
us some pointers (wink, wink)?

JP

--~--~---------~--~----~------------~-------~--~----~



Wall Street Journal article today - are things going down the drain for independent developers?

by Anil » Tue, 01 Jul 2008 22:04:03 GMT


 


--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. WeCon #1, The Nominees, and The Winner

ht <http://gpgo.in/DW>tp://gpgo.in/DW <http://gpgo.in/DW>
<http://gpgo.in/DW>Kompetisi mingguan lomba foto pake android yang diadakan
oleh fotodro...@googlegroups.com
Ini dia 5 karya foto nominasi terbaik...
juaranya?
Tunggu yaaaa...
stay tune...

Android juga bisa berguna kok di bidang art...gak cuma sekedar dioprek dan
gonta ganti ROM...
well...at least terbukti lah :)
*plotot ke segala arah

Follow us on twitter @gopegodotcom

----------------------------
@yopiesuryadi
www.gopego.com
http://about.me/yopie

-- 
===============

2. Custom Dialogs with big messages

I've been creating custom dialogs using the SDK docs:

http://developer.android.com/guide/topics/ui/dialogs.html#CustomDialog

What I've wanted to do is have a dialog with an extra checkbox below a
large chunk of text, so large in some cases that the text has to
scroll. The checkbox should be stuck at the bottom, always visible,
with the text above it. The dialog should resize as required to fit
the text, until the text can't fit and the text has to scroll.

I found that I could put the checkbox as a custom view as described in
the docs, and I could use setMessage for the text - and the text would
scroll - just like I wanted. The problem was as the text got long to
the point where it needed to scroll, it would also push the checkbox
view down beneath the dialog buttons where it couldn't be seen or
touched!

I've worked around this problem by adding a TextView to the View above
the Checkbox, then wrapping the whole lot in a ScrollView. The dialog
grows and shrinks with the message, the only issue being that the
Checkbox can scroll out of view, but at least it's still accessible.

The closest I've got is assigning a fixed height to the TextView, but
having to define a layout for every possible screen size and
orientation seems absurd, yet I can't think of any other way to end up
with an ideal layout.

Is this possible? Can anyone help me out here? Thanks.

-- 

3. Cannot use AXMLPrinter2 to translate binary xml correctly in Honeycomb-version apk

4. Screen rotation clears TextView

5. porting android to sony ericsson w960i

6. Android Community Leaders and Android Development Tools fireside chat meeting at AnDevCon

7. Launching notifications from core