● Android's defined tags
● Used to define some of the resources:
● Android Manifest
● Preferred way for defining UI elements:
– Separation of code
● Auto-generated: DO NOT EDIT
● Contains ID of the project resources
● Use findViewById and Resources object to get
access to the resources:
– E.g. Button = (Button)findViewById(R.id.button);
– E.g. getResources().getString(R.string.hello);
● Eclipse has a great UI creator
– Generates all the XML for you !
● Composed of View objects
● Can be specified for portrait or landscape
– Different designs for different orientation.
● A layout/activity is composed of Views and
● View is something that is visible.
– TextViews, Buttons,
android:id = “@+id/button”
android:layout_width = “fill_parent”
android:layout_height = “wrap_content”
android:text = “Button”/>
There are 3 ways
width and height:
Do not forget
to define us :)
You can change the
type of inputs as
● ViewGroups are the building blocks to Views:
– This is the <body> to your View
– One or more View can be grouped into a ViewGroup
● Types to ViewGroups:
– ScrollView*, etc.
● Each layout has something unique to it
● Each layout has a purpose !
… (TextViews, Buttons etc.)
Declaring the XML
(done in the
Unique for this ViewGroup
● Does not have any android:orientation.
● Affects the layouts inside it.
● Views are arranged according to references.
LinearLayout VS. RelativeLayout
Lets Unite !
<LinearLayout … >
<RelativeLayout … >
● You can use Viewgroups within Viewgroups :
Building a simple UI
Redirect to another page
with all the filled details
What is needed for this?
– <a href= “target”>page 2</a>
– Intent = Redirecting !
– But wait …
– Intent is used to call into android's drivers, other
applications as well.
– Powerful inter/intra application message-passing
● Modification in the Android Manifest:
Declares an activity
(an Activity subclass)
part of the application's
visual user interface.
The types of
that an app
can respond to
Adds a category
an intent filter
● In your main class:
Intent i = new Intent(MainActivity.this,
ClassName.class); // Instantiating the intent class
i.putExtra(“name”, value); // values to be sent
startActivity(i); // Starting the intent
● Another class:
Intent i = getIntent(); //getting the intent object
String name = i.getStringExtra(“name”); //getting value
from passed intent
Explaining it all
● Create your form
– UI interface
– Result interface
● Create two classes that extend the UI
● Add your ResultClass to the Android Manifest.
● Pass data from your FormClass to ResultClass using
What is Manifest ?
● Presents essential information about:
– The application to the Android system
● Information the system must have before it can run any
of the application's code.
● Name of the Java package for the application.
● It describes the components of the application — the activities, services, broadcast
receivers, and content providers.
● It determines which processes will host application components.
● It declares which permissions the application must have in order to access
protected parts of the API and interact with other applications.
● It also declares the permissions that others are required to have in order to interact
with the application's components.
● It lists the Instrumentation classes that provide profiling and other information as the
application is running. These declarations are present in the manifest only while the
application is being developed and tested; they're removed before the application is
● It declares the minimum level of the Android API that the application requires.
● It lists the libraries that the application must be linked against.
“Have you ever wondered
what happens when you press the back
button/ home button on android?”