Uploaded on

 

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
195
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
6
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Workshop Mobile Application Development
  • 2. The canvas is exactly what its name implies. It represents a surface that can have things drawn to it. Imagine it as a piece of paper that you can draw shapes and images on. The Canvas class provides methods for you to: Draw primitives such as simple shapes and paths  Draw bitmaps  Draw text  Clip drawing operations  Translate, scale, rotate, or otherwise transform the canvas's image  Save and restore drawing states
  • 3. The properties that a Paint object encapsulates are: Drawing Color  Primitive drawing style (solid 'fill' or outline 'stroke')  Stroke style attributes  Fill shader  Text drawing font attributes  Color filter  Mask filter  Transfer mode  Shadow layer 
  • 4.  Bitmap Every canvas has exactly one underlying Bitmap object. The bitmap holds the actual pixel data of the image you are working with. Whereas the Canvas class provides a high level interface to draw shapes, paths, text, and so on, the Bitmap class provides a more low-level interface to the image, allowing you to manipulate the pixels directly.
  • 5. <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.commonsware.android"> <uses-permission android:name="android.permission.ACCESS_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_GPS" /> <uses-permission android:name="android.permission.ACCESS_ASSISTED_GPS" /> <uses-permission android:name="android.permission.ACCESS_CELL_ID" /> <application> ... </application> </manifest>
  • 6. Shared Preferences  Store private primitive data in key-value pairs. Internal Storage  Store private data on the device memory. External Storage  Store public data on the shared external storage. SQLite Databases  Store structured data in a private database. Network Connection  Store data on the web with your own network server.
  • 7.  Android provides full support for SQLite databases. Any databases you create will be accessible by name to any class in the application, but not outside the application. public class DictionaryOpenHelper extends SQLiteOpenHelper { private static final int DATABASE_VERSION = 2; private static final String DICTIONARY_TABLE_NAME = "dictionary"; private static final String DICTIONARY_TABLE_CREATE = "CREATE TABLE " + DICTIONARY_TABLE_NAME + " (" + KEY_WORD + " TEXT, " + KEY_DEFINITION + " TEXT);"; DictionaryOpenHelper(Context context) { super(context, DATABASE_NAME, null, DATABASE_VERSION); } } @Override public void onCreate(SQLiteDatabase db) { db.execSQL(DICTIONARY_TABLE_CREATE); }
  • 8. Augmented Campus Reality • camera + maps + compass = heads up info Games • multi-player (bluetooth, wifi, cell) • location-based (scavenger hunt) Custom overlays for maps • weather, traffic, friends Web scraping • news filters • sport scores • news eliminators Distributed computing? • 10,000 phones all donating their idle time Shared whiteboard
  • 9. RELEASE PROCESS Prepare for Build Perform Build “Release Candidate” Thoroughly Test Build Got Bugs? Fix Bugs! Got Bugs? No Bugs? Publish Release Test Packaged Release Candidate Package and Sign Package
  • 10. ONLINE ANDROID RESOURCES ➲  ➲  ➲  ➲  ➲  Android developer website http://developer.android.com Open Handset Alliance http://www.openhandsetalliance.com Android Market http://market.android.com/publish Android libraries and extensions http://openintents.org Android developer forum http://www.anddev.org
  • 11. OUTLOOK ➲ Android will continue rapid growth  ➲ Handsets will be major market  ➲ Expected to be #1 smartphone by 2014 tablets and netbooks significant fringe Google will guide but not rule Android Telcos want to differentiate and have image Telcos want to lock users Telco aims conflict with developers and update process Google is expected to impose more uniformity • System minimum requirements • GUI design
  • 12. SUMMARY Solid, proven, popular, open platform ➲ Used on wide range of devices ➲ Support from Google, OEMs, telcoms ➲ Low barriers to entry ➲ Major opportunity for new developers ➲ Creativity, hard work, persistence ➲