The San Francisco Android User Group Message Board › Discussion Forum › Google I/O BootCamp open for registration
| Aleksandar Gargent... | |
|
|
Folks,
We just learned from Stephanie Liu at Google about this. They are opening registration for I/O BootCamp today. Full Sites page + registration: http://sites.google.c... The event will be held the day before Google I/O (Tuesday, May 18th, from 2-8pm), and will be smaller & more intimate. It will be free, and open to people who have already registered for the main conference. That is an important point. Check your confirmation email for your I/O registration and be sure to enter your email address and confirmation code from that email when registering for I/O BootCamp. They will be cross checking against this information from I/O registrations when processing BootCamp registrations. BootCamp will be focused on 101 sessions, hands-on lab sessions, and BarCamp-style community-led discussions. BootCamp capacity is much more limited than the main conference, so if you are planning on coming to I/O, register soon for both ASAP! Let me know if you have any questions. Cheers, Sasa --- Aleksandar (Sasa) Gargenta Marakana Inc. |
| Alan Musselman | |
|
|
Cool!
I like to develop, but feel that there is a serious hole around prototyping/conceptualizing Android based applications. I can't tell you how many times I prototyped an app/game and kept iterating and building on top of it to make it better. Its extremely critical and probably the most important step in the entire workflow from engineering to product management.. Last thing you need to do is realize you forgot a crucial workflow and have to build the user flow/experience in development cycle. This can be a major pain point and make everyone work harder when they dont have too. I submitted a question/topic that would be useful for everyone. http://www.google.com... Cheers! //Alan |
| mathiastck | |
|
|
Its true that Android gives you lots of different ways to create the same product.
I like to break my apps up into lots of different activities, that are loosely linked. That way if an activity gets replaced with an AppWidget or service or whatever its not a problem. I also tend to follow an Agile Methodology focused on building discrete demoable components that I do then demo. Its also good to use content providers, URI patterns and to create custom mimetypes, that way other developers can fire off your discrete component. Integrate everything! -Matt Kanninen -Senior Android Developer |