0% found this document useful (0 votes)
13 views11 pages

MAD

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views11 pages

MAD

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

MAD – UNIT – 5 Taking Apps to Market and Wireless Language :

1) Versioning :
 Versioning in Android refers to the process of assigning a unique
version number to each update of an Android app. This is done to
track changes, updates, and maintenance of the app over time.

 In Android, versioning is done using two main components:

1. Version Code (android:versionCode): An integer value that


represents the version of the app. It's used internally by the Android
system to determine whether one version is newer than another.
Typically, it's incremented by 1 for each new version.

2. Version Name (android:versionName): A string value that


represents the version of the app in a human-readable format (e.g.,
1.0.0, 2.1.1, etc.). This is the version number that's displayed to users
in the Play Store and app settings.

 Proper versioning is essential for:

Ensuring users receive updates correctly


Tracking changes and updates in the app's development process
Maintaining compatibility with different Android versions and devices

 When updating an app, developers should increment the version


code and update the version name to reflect the changes made.

2) Signing & Packaging Mobile Apps :


 Signing and packaging mobile apps in Android involves the following
steps:
1) Signing:

1. Generate a keystore: Create a keystore file (e.g., myapp.keystore)


using tools like Keytool or Android Studio.
2. Create a key: Generate a private key (e.g., myappkey) within the
keystore.
3. Set an alias: Assign an alias to the key (e.g., myappalias).
 Packaging:-

1. Compile code: Compile the app's source code into an APK (Android
Package File).
2. Package APK: Package the compiled code into an APK file.
3. Sign APK: Sign the APK with the private key from the keystore.
4. Align APK: Align the signed APK with the zipalign tool for optimized
memory usage.

 Final steps:

1. Export signed APK: Export the signed and aligned APK from
Android Studio or the command line.
2. Upload to Play Store: Upload the final APK to the Google Play Store
for distribution.

 Benefits:

1) Ensures app authenticity and integrity


2) Verifies app authorship
3) Enables app updates and maintenance
4) Required for Google Play Store distribution

 Remember to keep your keystore and private key secure, as they're


used to sign and verify your app's identity.

2) Distributing Apps on Mobile Market Place :


 Distributing apps on mobile marketplaces involves the following
steps:

 Google Play Store:

1. Create a developer account: Sign up for a Google Play Developer


account ($25 one-time fee).
2. Prepare app for release: Ensure app meets guidelines and is
properly signed and packaged.
3. Create a store listing: Enter app details, screenshots, and
promotional images.
4. Set pricing and distribution: Choose pricing, countries, and device
targets.
5. Publish app: Upload and submit app for review.
6. Monitor and update: Track app performance, user feedback, and
update as needed.

 Apple App Store:

1. Create a developer account: Enroll in the Apple Developer


Program ($99/year).
2. Prepare app for release: Ensure app meets guidelines and is
properly signed and packaged.
3. Create a store listing: Enter app details, screenshots, and
promotional images.
4. Set pricing and distribution: Choose pricing, countries, and device
targets.
5. Submit for review: Upload and submit app for review.
6. Monitor and update: Track app performance, user feedback, and
update as needed.

 Other marketplaces:

1. Amazon Appstore: Similar process to Google Play Store.


2. Huawei AppGallery: Similar process to Google Play Store.
3. Samsung Galaxy Store: Similar process to Google Play Store.

 Additional tips:

1) Ensure app meets each marketplace's guidelines and policies.


2) Optimize app store listings for visibility and conversion.
3) Utilize analytics and user feedback for continuous improvement.
4) Consider offering in-app purchases, subscriptions, or ads for
monetization.
5) Keep app updated to maintain user engagement and retention.
3) Wireless Languages :
1) Markup Languages :
 Markup languages are used to add structure and formatting to text
documents, making them readable by both humans and machines.
Here are some common markup languages:

1. HTML (Hypertext Markup Language): Used for creating web pages


and web applications.
2. XML (Extensible Markup Language): Used for storing and
transporting data in a format that's both human-readable and
machine-readable.
3. Markdown: A lightweight markup language used for creating
formatted text documents, often used in blogging, documentation,
and chat applications.
4. SGML (Standard Generalized Markup Language): A precursor to
HTML and XML, used for defining document structures.
5. LaTeX: A markup language used for creating scientific and
academic documents, particularly in mathematics, physics, and
engineering.
6. RSS (Really Simple Syndication): A markup language used for
creating web feeds, allowing users to subscribe to content updates.
7. Atom: A markup language used for creating web feeds, similar to
RSS.
8. XHTML (Extensible Hypertext Markup Language): A markup
language that combines HTML and XML, used for creating web pages
that are both human-readable and machine-readable.

 These markup languages use tags, elements, and attributes to add


meaning and structure to text documents, making them essential
tools for web development, data exchange, and document creation.

4) HDML :
 HDML (Handheld Device Markup Language) is a markup language
used for creating web pages and applications on handheld devices,
including Android devices. However, HDML has largely been replaced
by HTML5, CSS3, and JavaScript, which offer more advanced features
and better support for modern mobile devices.
 In Android, you can use HDML to create simple web pages and
applications, but it's not the recommended approach. Instead, you
can use:

1. HTML5: For creating web pages and hybrid applications using web
technologies.
2. Android XML: For creating native Android applications, using XML
to define user interfaces and layouts.
3. Kotlin or Java: For creating native Android applications, using these
programming languages to write app logic.

 If you still want to use HDML in Android, you can:

1. Create HDML files with a .hdml extension.


2. Use the WebView component to display HDML content in your
Android app.
3. Utilize the HdmlParser class to parse HDML content and render it
in your app.

 Keep in mind that HDML has limitations and is not as widely


supported as modern web technologies. For most Android
development, HTML5, CSS3, and JavaScript are recommended for
web-based applications, while Kotlin or Java are recommended for
native applications.

5) WML :
 WML (Wireless Markup Language) is a markup language used for
creating web pages and applications on mobile devices, including
Android devices. However, WML is an older technology and has
largely been replaced by HTML5, CSS3, and JavaScript.

 In Android, WML is not directly supported, and it's not


recommended to use it for new development. Instead, you can use:

1. HTML5: For creating web pages and hybrid applications using web
technologies.
2. Android XML: For creating native Android applications, using XML
to define user interfaces and layouts.
3. Kotlin or Java: For creating native Android applications, using these
programming languages to write app logic.

 If you need to support older devices or legacy applications that use


WML, you can:

1. Use a third-party library or parser to render WML content in your


Android app.
2. Convert WML content to HTML5 or Android XML for better
compatibility.

 Keep in mind that WML has limitations and is not as widely supported
as modern web technologies. For most Android development,
HTML5, CSS3, and JavaScript are recommended for web-based
applications, while Kotlin or Java are recommended for native
applications.

 Here's a rough estimate of the timeline:

WML: Used in early 2000s for mobile web development


HDML: Used in mid-2000s for mobile web development
HTML5: Became widely adopted around 2010 for mobile and web
development

 Note that both WML and HDML are considered legacy technologies,
and it's recommended to use modern technologies for new
development.

6) HTML :
 HTML can be used in Android development in several ways:

1. WebView: A UI component that displays web pages or HTML


content within an Android app.
2. Hybrid Apps: Build apps using HTML, CSS, and JavaScript, then
wrap them in a native Android container using tools like Cordova or
PhoneGap.
3. Web-based Apps: Create web apps that run in the Android browser
or other web browsers, using HTML, CSS, and JavaScript.

 To use HTML in Android:

1. Create HTML files: Write HTML code in a text editor or IDE.


2. Use WebView: Add a WebView component to your Android layout
XML file.
3. Load HTML content: Use the loadUrl() or loadData() method to
display HTML content in the WebView.

 Example:

<WebView
android:id="@+id/webview"
android:layout_width="match_parent"
android:layout_height="match_parent" />

WebView webView = findViewById(R.id.webview);


webView.loadUrl("file:///android_asset/index.html");

 You can also use HTML to create:

1) Alert dialogs: Use HTML to create custom alert dialogs.


2) Help screens: Display HTML content as help screens within your
app.
3) Data visualization: Use HTML and JavaScript libraries like D3.js to
create interactive data visualizations.

 Remember to consider security and performance when using HTML


in Android development.
7) CHTML :
 cHTML (Compact HTML) is a subset of HTML used for creating web
pages on mobile devices, including Android devices. However, cHTML
is an older technology and has largely been replaced by HTML5, CSS3,
and JavaScript.

 In Android, cHTML is not directly supported, and it's not


recommended to use it for new development. Instead, you can use:
1. HTML5: For creating web pages and hybrid applications using web
technologies.
2. Android XML: For creating native Android applications, using XML
to define user interfaces and layouts.
3. Kotlin or Java: For creating native Android applications, using these
programming languages to write app logic.

 If you need to support older devices or legacy applications that use


cHTML, you can:

1. Use a third-party library or parser to render cHTML content in your


Android app.
2. Convert cHTML content to HTML5 or Android XML for better
compatibility.

 Keep in mind that cHTML has limitations and is not as widely


supported as modern web technologies. For most Android
development, HTML5, CSS3, and JavaScript are recommended for
web-based applications, while Kotlin or Java are recommended for
native applications.

 Here's a rough estimate of the timeline:

1) cHTML: Used in late 1990s and early 2000s for mobile web
development
2) WML and HDML: Used in early 2000s for mobile web
development
3) HTML5: Became widely adopted around 2010 for mobile and web
development
8) XHTML :
 XHTML (Extensible Hypertext Markup Language) is a markup
language that combines HTML and XML. In Android, XHTML can be
used in the following ways:

1. WebView: Display XHTML content in a WebView component, just


like HTML content.
2. XmlPullParser: Parse XHTML content using the XmlPullParser class.
3. Jsoup: Use the Jsoup library to parse and manipulate XHTML
content.

 To use XHTML in Android:

1. Create XHTML files: Write XHTML code in a text editor or IDE.


2. Use WebView: Add a WebView component to your Android layout
XML file.
3. Load XHTML content: Use the loadUrl() or loadData() method to
display XHTML content in the WebView.

 Example:

<WebView
android:id="@+id/webview"
android:layout_width="match_parent"
android:layout_height="match_parent" />
WebView webView = findViewById(R.id.webview);
webView.loadUrl("file:///android_asset/index.xhtml");

 XHTML is similar to HTML, but with stricter syntax rules, making it


easier to parse and manipulate. However, for most Android
development, HTML5 is recommended over XHTML.

 Note that XHTML has different versions, such as:

1) XHTML 1.0
2) XHTML 1.1
3) XHTML 2.0 (abandoned)
4) XHTML5 (a variant of HTML5)
 Make sure to specify the correct XHTML version in your document's
DOCTYPE declaration.

9) VoiceXML :
 VoiceXML (Voice Extensible Markup Language) is a markup language
used for creating voice user interfaces, particularly for interactive
voice response (IVR) systems and voice assistants. In Android,
VoiceXML can be used in the following ways:

1. VoiceXML interpreters: Integrate a VoiceXML interpreter library,


such as Voxeo's VoiceXML interpreter or the OpenVXI VoiceXML
interpreter, into your Android app to parse and execute VoiceXML
documents.
2. TTS (Text-to-Speech) engines: Utilize Android's built-in TTS engine
or third-party TTS engines, like eSpeak or Flite, to synthesize
VoiceXML content into speech.
3. ASR (Automatic Speech Recognition) engines: Integrate third-
party ASR engines, like Google's Speech Recognition API or Nuance's
Dragon Mobile SDK, to recognize user speech and interact with
VoiceXML applications.

 To use VoiceXML in Android:

1. Create VoiceXML documents: Write VoiceXML code in a text editor


or IDE.
2. Integrate a VoiceXML interpreter: Add the interpreter library to
your Android project and use it to parse and execute VoiceXML
documents.
3. Use TTS and ASR engines: Integrate TTS and ASR engines to
synthesize VoiceXML content and recognize user speech.

 Example:

<?xml version="1.0" encoding="UTF-8"?>


<vxml version="2.1">
<form>
<block>
<prompt>Hello, welcome to our voice application!</prompt>
</block>
</form>
</vxml>

 Note that VoiceXML is not directly supported by Android, so you'll


need to rely on third-party libraries and engines to implement
VoiceXML functionality. Additionally, VoiceXML is primarily used for
IVR systems and voice assistants, so its adoption in Android apps
might be limited.

You might also like