David Welton: Munich Android Mobile Meeting Report
I'm a bit tired after driving up to Munich for the Android developer meeting, hosted by Google, and being "on" all day, but it was worth it. I was a bit apprehensive that it might be too 'introductory' in the sense of the Google guys telling you in person things that you could have easily looked up on the web, without spending a bunch of time driving around Austria and Bavaria. Fortunately, that wasn't the case. There was some of that, but also plenty of unstructured time to chat with Dan Morrill and Jason Chen, the two Google "Developer Advocates", who are both very friendly, informative and informed, approachable and put a lot of energy into what they do, despite being a bit tired from flying over from the US. It was nice to get a chance to talk with them, and considering that the platform is still changing, useful as well, because they were definitely listening to what people had to say to them. My thanks to them for a job well done.
Here are some "impressions" I took away - note that they're not what anyone said, just ideas I got about what they said:
- Source code is being released when handsets ship because they want to work very closely with the hardware partners to make sure the phone experience is good (they said this). They want to "set the bar high", and they probably run the risk of someone snatching the code and slapping together a phone if they let out the source code to early. (They definitely didn't say this, it's just me connecting the dots).
- Despite interest for 'other languages', it really looks like they want everything to go through Dalvik in some way or another. Clearly, at some point in the future, there will be specs for writing Dalvik byte code.
- They won't talk about the upgrade strategy, something I asked about. I want to know that as a developer, I won't be stuck with N combinations of things that I have to support over the years. I want to know how they'll minimize that pain, but they're not currently able to discuss it.
- Talking with other people attending, there seemed to be some doubts about security and permissions for user data, since Android is moving away from the j2me "everything is private" model, to a model where data can be shared between apps, which opens up lots of good things, but also some potentially bad ones as well.
...install a 
The not-yet-so-mighty project build tool I'm writing (codenamed "dammit") just compiled itself for the first time (took 40 seconds :-P ). It is probably not that usable yet, as it lacks dependency checking and thus always recompiles everything -- fixing that is the plan for tonight.
So far, all it does is compile everything it can find and recognise in a directory and link it to a program; the plan for the future is not to add too much to that, mainly new project types like libraries and new input languages.
* Thanks to Albert (aacid) for
I speculate that most of what we do for Debian squares with what
others do for their respective distro. Thus, it should be possible
to identify a conceptual workflow applicable to all distros,
consolidate individual workflows on a per-package basis, and profit
from each other. Jonathan let me have the after-afternoon-coffee
slot of the
See
As I
After a three and a half week test drive during my last year’s summer
holidays and much consideration about the configuration, I finally
ordered a
I spent a good few hours today on creating a preliminary schedule for
the Debian Developer's room at FOSDEM 2008. Just as I had finished it
and sent it to the speakers to get their feedback before declaring it
final, I received a reminder from the FOSDEM organizers that the
schedule is due by the end of this week. My timing is impeccable :-)
Having said that, the schedule is full. If you wanted to do a talk at
FOSDEM, you're probably too late by now. Try again next year.
Time to start focusing on the booth now, I guess...
