Reactive Android Development

Slides:



Advertisements
Similar presentations
Google Android Introduction to Mobile Computing. Android is part of the build a better phone process Open Handset Alliance produces Android Comprises.
Advertisements

Android OS : Core Concepts Dr. Jeyakesavan Veerasamy Sr. Lecturer University of Texas at Dallas
Application Fundamentals Android Development. Announcements Posting in D2L Tutorials.
Android Security. N-Degree of Separation Applications can be thought as composed by Main Functionality Several Non-functional Concerns Security is a non-functional.
Android activities 1 CS300. What makes an app?  Activities: presentation layer  Services: invisible workers  Content Providers: databases  Intents:
Android 101 Application Fundamentals January 29, 2010.
Mobile Programming Pertemuan 6 Presented by Mulyono Poltek NSC Surabaya.
Android Programming Beomjoo Seo Sep., 12 CS5248 Fall 2012.
INTERNATIONAL SUMMER ACADEMIC COURSE UNIVESITY OF NIS ISAC – Android programming.
Emerging Platform#4: Android Bina Ramamurthy.  Android is an Operating system.  Android is an emerging platform for mobile devices.  Initially developed.
Android Middleware Bo Pang
박 종 혁 컴퓨터 보안 및 운영체제 연구실 MobiSys '11 Proceedings of the 9th international conference on Mobile systems, applications,
Google Maps Android API v2 吳俊興 國立高雄大學 資訊工程學系 CSF645 – Mobile Computing 行動計算
CS5103 Software Engineering Lecture 08 Android Development II.
© Keren Kalif Intro to Android Development Written by Keren Kalif, Edited by Liron Blecher Contains slides from Google I/O presentation.
Software Architecture of Android Yaodong Bi, Ph.D. Department of Computing Sciences University of Scranton.
Favorite Twitter® Searches App Android How to Program © by Pearson Education, Inc. All Rights Reserved.
Rajab Davudov. Agenda Eclipse, ADT and Android SDK APK file Fundamentals – Activity – Service – Content Provider – Broadcast Receiver – Intent Hello World.
This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit
Mobile Application Development using Android Lecture 2.
Erika Chin Adrienne Porter Felt Kate Greenwood David Wagner University of California Berkeley MobiSys 2011.
CS378 - Mobile Computing Intents.
16 Services and Broadcast Receivers CSNB544 Mobile Application Development Thanks to Utexas Austin.
Android for Java Developers Denver Java Users Group Jan 11, Mike
Overview of Android Application Development
CS378 - Mobile Computing Intents. Allow us to use applications and components that are part of Android System – start activities – start services – deliver.
COMP 365 Android Development.  Every android application has a manifest file called AndroidManifest.xml  Found in the Project folder  Contains critical.
Mobile Application Security on Android Originally presented by Jesse Burns at Black Hat
1 Android Introduction Platform Overview. 2 What is Android?  Android is a software stack for mobile devices that includes an operating system, middleware.
Lecture 2: Android Concepts
Resources & Android Manifest Калин Кадиев Astea Solutions AD.
NTHU CS ISLAB 國立清華大學 資訊工程研究所 資訊安全實驗室 Semantically Rich Application- Centric Security in Android Machigar Ongtang, Stephen McLaughlin, William Enck and.
6/12/2016 TOPS Technologies- Android training -
The Ingredients of Android Applications. A simple application in a process In a classical programming environment, the OS would load the program code.
Editing a Twitter search. Viewing search results in a browser.
CS371m - Mobile Computing Intents 1. Allow us to use applications and components that are already part of Android System – start activities – start services.
CHAPTER 1 part 1 Introduction. Chapter objectives: Understand Android Learn the differences between Java and Android Java Examine the Android project.
Introduction to Android Programming
Introduction to Android Chapter 1 1. Objectives Understand what Android is Learn the differences between Java and Android Java Examine the Android project.
Android Mobile Application Development
Android Application -Architecture.
Mobile Applications (Android Programming)
Android Mobile Application Development
Lecture 2: Android Concepts
Android 01: Fundamentals
Tracking device movements
CS371m - Mobile Computing Services and Broadcast Receivers
Reactive Android Development
Instructor: Mazhar Hussain
Android System Security
Android Runtime – Dalvik VM
Android Studio, Android System Basics and Git
Android.
MAD.
Activities and Intents
Mobile Device Development
Android Programming Lecture 5
Reactive Android Development
CS5103 Software Engineering
Reactive Android Development
CS323 Android Topics Network Basics for an Android App
Android Developer Fundamentals V2
Activities and Intents
Android Platform, Android App Basic Components
Emerging Platform#3 Android & Programming an App
It is used to Start an Activity Start a Service Deliver a Broadcast
Introduction to Android
Lecture 2: Android Concepts
Preference Activity class
CA16R405 - Mobile Application Development (Theory)
Presentation transcript:

Reactive Android Development CS 4593-02T & CS 5463-01T Summer 2016

Manifest "header" <uses-permission /> <permission /> <permission-tree /> <permission-group /> <instrumentation /> <uses-sdk /> <uses-feature /> <supports-screens /> <compatible-screens /> <supports-gl-texture />

Manifest: permissions <uses-permission android:name="string" android:maxSdkVersion="integer" /> Requests permissions that must be granted by the user

Manifest: permissions <permission android:description="string resource" android:icon="drawable resource" android:label="string resource" android:name="string" android:permissionGroup="string" android:protectionLevel=[ "normal" | "dangerous" | "signature" | "signatureOrSystem"] /> Defines a new kind of permission

Manifest: Permissions <permission-tree android:icon="drawable resource" android:label="string resource" ] android:name="string" /> Provides a hierarchy for categorizing permissions

Manifest: Permissions <permission-group android:description="string resource" android:icon="drawable resource" android:label="string resource" android:name="string" /> Provides a way to group declared permissions so that they will be presented to the user at the same time.

Manifest: instrumentation Used to register a class for debugging or otherwise monitoring the application

Manifest: uses-sdk Used to declare the minimum and maximum SDK versions on which this app can run

Manifest: uses-configuration Describes hardware/software configuration required for this app. Most apps should not use this tag!

Manifest: uses-feature android:name="string" android:required=["true" | "false"] android:glEsVersion="integer" /> Defines hardware and software features that may be required or desired for the app. Can be declared more than once.

Manifest: supports-screens Can limit supported screen sizes (in broad catagories) Small Normal Large XLarge

Manifest: compatible-screens Information only, not used at runtime But can affect availability on Google Play store If defined, you must list all screens that you support Normally, you should not use this element

Manifest: supports-gl-texture Used to declare texture (bitmap) compression formats that your app supports Can be used to limit the devices that can see your app based on GPU capabilities If not specified, no filtering based on GL texture formats will be applied.

Manifest: application The only required element in a manifest! Declares Activities Services (non-UI background code) Receivers (listens for broadcast messages) Providers (provides data to multiple components/ apps) <activity-alias /> <uses-library />

Manifest: application/activity <activity> <intent-filter> <action/> <category/> <data/> </intent-filter> <meta-data/> </activity>

Manifest: example intent-filter <activity android:name="ShareActivity"> <intent-filter> <action android:name="android.intent.action.SEND"/> <category android:name="android.intent.category.DEFAULT"/> <data android:mimeType="text/plain"/> </intent-filter> </activity>

Manifest: application/provider <provider> <grant-uri-permission /> <meta-data /> <path-permission /> </provider>

Lifecycle

Lifecycle

Lifecycle

Lifecycle

Lifecycle

Persistence: Key-Value Pairs getPreferences() When you only need one properties file getSharedPreferences Named preferences file

Persistence Writing Reading Uses a SharedPreferences.Editor editor = getPreferences().edit() editor.putInt("IntKey", 5); Reading Just uses the SharedPreferences object getPreferences().getInt("IntKey", 20);