Sogeti - Android tech track presentation - 24 february 2011
•Download as PPT, PDF•
1 like•872 views
Presentation of the Android Tech Track by Sogeti. Presentation by: * Ben Stroobants * Kenneth Van Rumste * Mark Fonteyne * Mikhail Panshenskov * Alexis Mathieux * Geoffroy Mispelaere * Tom Pluym
![Android Tech Track Mobile App development 24 February 2011 Sogeti, Evere ,[object Object]](https://image.slidesharecdn.com/androidtechtrackpresentationd-d-24february2011-110301013831-phpapp01/85/Sogeti-Android-tech-track-presentation-24-february-2011-1-320.jpg)
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Sogeti - Android tech track presentation - 24 february 2011
Similar to Sogeti - Android tech track presentation - 24 february 2011 (20)
Recently uploaded
Recently uploaded (20)
Sogeti - Android tech track presentation - 24 february 2011
- 4. Introduction: Smartphones & Mobile Apps
- 11. Android The Open Handset Alliance (OHA)
- 14. Android Recent version history- market share
- 20. Android Global market importance
- 41. Approach / Actions: iPhone
Editor's Notes
- Welcome: Mobile App development where we present the results of the Android Tech Track 5 presenters 7 participants: presenters + Mark Fonteyne + Mikhail Panshenskov Goal:
- What? handheld computers integrated with a mobile telephone usually allows the user to install and run more advanced applications run complete operating system software providing a platform for application developers it integrates a wide range of features into a consumer-oriented device among which satellite navigation (GPS), a megapixel camera with autofocus and LED flash, 3G and wi-fi connectivity, motion detection (accelerometers, tilt sensors), … 2001: Kyocera 6035 by Palm Inc.; combined features of a PDA and a wireless phone e.g. dial from contact list and limited web browsing 2002: Blackberry (here Blackberry 7250); device optimized for wireless email use 2007: Nokia N95: GPS, a 5 megapixel camera with autofocus and LED flash, 3G and wi-fi connectivity and TV-out 2007: later in 2007, Apple releases original iPhone; controlled mainly through its multi-touchscreen marks the starting point for broad consumer adaptation of the smartphone device 2008: Android 2008: App Store + Android Market 2010: Windows Phone 7, limited success 2011: iPhone + Android, RIM and Nokia struggle with perception of being old-fashioned.
- One of the distinct features of a smartphone is that one can install apps on it. Multi-channel communication: e-mail, sms, website, phone, store, paper catalogue, snail mail etc. Channel it is most compared with is a (mobile) website.
- New versions: Distribution model: put on webserver Apps: app stores
- multi-channel: e-mail, sms, website, store, paper catalogue, snail mail etc e.g. Lego: was loosing appeal in the market to Adapted strategy. Created different brands Multi-channel approach: stores, websites, booklets New functionality in apps. Example: Mindstorms Installs: 10,000 – 50,000 How To Tie a Tie : Killer app : 500,000 – 1,000,000 installs (android market) app fits the format of the smartphone; mobile website wouldn’t be so user friendly; videos on internet Almost as simple and cheap as it can get BBC
- Add product - productcode - barcoce - promotion 2. Sign in 3. Promotions 4. Order
- GitHub: advantages: Internet based: easily accessible Git: distributed source control system Server: For real connectivity Tomcat Spring framework Spring security modules Options: publicly accessible instance from Sogeti / Amazon cloud
- Original planning Participants: Kenneth Van Rumste, Mark Fonteyne, Mikhail Panshenskov, Ben Stroobants, Alexis Mathieux, Geoffroy Mispelaere, Tom Pluym Extra: initial app by Kenneth Van Rumste Weekly meeting: Synchronize work: Tasks completed Identify work items Assign tasks
- Intent: abstract description of an operation to be performed provides a facility for performing late runtime binding between the code in different applications most significant use is in the launching of activities , where it can be thought of as the glue between activities
- Activity class: An activity is a single, focused thing that the user can do . Almost all activities interact with the user , so the Activity class takes care of creating a window for you in which you can place your on UI Lifecycle, e.g. in onPause() one can save somet state Start activities: see barcoce scanner Handle screen events (if not by view) Context menus