Bangalore Android Developers Meetup 8 : Live Event
1:57PM
And we come to an end of the BAUG meetup 8!
App Demos
Panorama of Locations : Crowdsourced
http://goo.gl/1nKuY
12:47PM
Google is one of the biggest commercial companies. Fully opensourcing Android will not be in full interests of Google.
Comment from Audience "Opensource to me is modifying sourcecode as per my wish and not get sued."
Comment from Audience "Google is taking the advantage of the word OPEN".
There is difference between in Open and Opensource.
Open for users means, get app from anywhere and run it in your phone.
Open for OEMs means modify the Source as you wish and don't bother about it.
Google doesn't agree to bugs too.
12:31PM
Panel Discussion on "Is Android Really Open?"
Important discussion it must be!
5 Panelists : 2 Saying it is open, 3 say not so much!
There are diff levels of opensource, there are part of it opensourced by Google, but your phone still contains closed source components too.
There is practically no way to submit code / patch to Android unless you are a OHA dev.
Samsung published its Sources!
If honeycomb is not kept until wraps until its fully baked, otherwise it will fail like the java on phones which are incompatible with each other.
Who is concerned whether Android is open or not? User, Dev, App Producers, OEMs, Carriers?
11:45AM
Ravi's Session on Copyrights and Licenses
Discussion is a prelude to the panel discussion about Android Openness.
Don't copy code off the internet if there is no conditions mentioned. You might violate the copyright law and be doomed for the lifetime.
Public Domain is stuff not protected by copyright laws. Shakespeare, Ramayana are Public Domain.
OSS is not Public Domain, it is rather licensed sofware, more like windows, but with different conditions.
Apache : Give me Credit
Firefox, Eclipse : Give me Fixes
GPL : Give me everything.
11:35AM
Least text inputs
avoid complex interactions
Better feedback in the apps
High Contrast text is better!
Amrit's session comes to end!
11:17AM
Design Considerations
Mobile is not desktop!
Optimize screen to show important info and actions
Consistent UI design
Usability Testing.
Lotsa discussion about usability!
Do not make your app look like its on another (i)platform!
11:11AM
Technical Challenges :
balance in portability and platform capabilities
Limited screen size
Diff resolutions, screen sizes, orientations.
Battery Life,
limited resources, input devices
Unpredictable connectivity
High bandwidth cost etc
11:05AM
Amrit takes over from Sudar, for his session "Android Best Practices"
10:40AM
Talks about Arduino shields start. Sudar displays bluetooth shield, Ethernet shield etc.
Discussions about Host and peripherals.
ADB is a light protocol, which is going to be used to communicate between Arduino, which will have a USB Host shield, and the Android device.
Logcat will carry our messages/commands.
An app to blink lights on the Arduino shield is demoed. Looks cool. Gonna order a board now!
The source code for the demo is available at Sudar's github
Discussions about real life implementations, program size, bootloaders, wiimotes etc.
10:28AM
Sudar takes the dais, for the arduino talk.
But with Arduino board, you can!
10:20AM
Intro session started. A web / mobile app dev, a Prod manager, An retired Electronics Engineer and Arduino fan are with us.
Many Services Engineers are curious about Android here.
An LFY editor, many oracle guys(!).
And One man company working on Android Tablets.
The intro is over, without my intro :(
10:15AM
People trickling in! And Akshay already started with the intro.
Very few people building Honeycomb apps. DroidCon will be in Bangalore in Sep-Oct this year.
There is a college kid here!
10:00 AM
Very less people as of now!
And here we go!
And we come to an end of the BAUG meetup 8!
App Demos
Panorama of Locations : Crowdsourced
http://goo.gl/1nKuY
Coupon Meter
App to do something with Sodexho coupons.
Really cool one, shows you what denominations to use while in a counter. Locates where how much was spent. Tries to make cash transaction as 0. 12:47PM
Google is one of the biggest commercial companies. Fully opensourcing Android will not be in full interests of Google.
Comment from Audience "Opensource to me is modifying sourcecode as per my wish and not get sued."
Comment from Audience "Google is taking the advantage of the word OPEN".
There is difference between in Open and Opensource.
Open for users means, get app from anywhere and run it in your phone.
Open for OEMs means modify the Source as you wish and don't bother about it.
Google doesn't agree to bugs too.
12:31PM
Panel Discussion on "Is Android Really Open?"
Important discussion it must be!
5 Panelists : 2 Saying it is open, 3 say not so much!
There are diff levels of opensource, there are part of it opensourced by Google, but your phone still contains closed source components too.
There is practically no way to submit code / patch to Android unless you are a OHA dev.
Samsung published its Sources!
If honeycomb is not kept until wraps until its fully baked, otherwise it will fail like the java on phones which are incompatible with each other.
Who is concerned whether Android is open or not? User, Dev, App Producers, OEMs, Carriers?
11:45AM
Ravi's Session on Copyrights and Licenses
Discussion is a prelude to the panel discussion about Android Openness.
Don't copy code off the internet if there is no conditions mentioned. You might violate the copyright law and be doomed for the lifetime.
Public Domain is stuff not protected by copyright laws. Shakespeare, Ramayana are Public Domain.
OSS is not Public Domain, it is rather licensed sofware, more like windows, but with different conditions.
Apache : Give me Credit
Firefox, Eclipse : Give me Fixes
GPL : Give me everything.
11:35AM
Least text inputs
avoid complex interactions
Better feedback in the apps
High Contrast text is better!
Amrit's session comes to end!
11:17AM
Design Considerations
Mobile is not desktop!
Optimize screen to show important info and actions
Consistent UI design
Usability Testing.
Lotsa discussion about usability!
Do not make your app look like its on another (i)platform!
11:11AM
Technical Challenges :
balance in portability and platform capabilities
Limited screen size
Diff resolutions, screen sizes, orientations.
Battery Life,
limited resources, input devices
Unpredictable connectivity
High bandwidth cost etc
11:05AM
Amrit takes over from Sudar, for his session "Android Best Practices"
The first one, Over Optimization.
The key challenges are, time to market, multiple OS version support, Diff form factors, Monetization.10:40AM
Talks about Arduino shields start. Sudar displays bluetooth shield, Ethernet shield etc.
Discussions about Host and peripherals.
ADB is a light protocol, which is going to be used to communicate between Arduino, which will have a USB Host shield, and the Android device.
Logcat will carry our messages/commands.
An app to blink lights on the Arduino shield is demoed. Looks cool. Gonna order a board now!
The source code for the demo is available at Sudar's github
Discussions about real life implementations, program size, bootloaders, wiimotes etc.
10:28AM
Sudar takes the dais, for the arduino talk.
Why Arduino?
Can you control the lights with the Android device alone? Nope!But with Arduino board, you can!
A blurry snapshot of Arduino IDE
A blinking program is written and is demoed.
Intro session started. A web / mobile app dev, a Prod manager, An retired Electronics Engineer and Arduino fan are with us.
Many Services Engineers are curious about Android here.
An LFY editor, many oracle guys(!).
And One man company working on Android Tablets.
The intro is over, without my intro :(
10:15AM
People trickling in! And Akshay already started with the intro.
There is a college kid here!
10:00 AM
Very less people as of now!
And here we go!
Comments