Modifying the displayed utility label on the Android working system entails altering the string useful resource that defines the applying’s title. This title is what customers see on their residence display screen, within the app drawer, and within the utility administration settings. For instance, an utility internally named “ProjectPhoenix” is likely to be displayed as “Phoenix” or “Phoenix App” to the consumer. This customization is achieved via modifications to the applying’s assets file, particularly the `strings.xml` file throughout the utility’s venture listing.
The flexibility to customise the applying’s displayed label is essential for branding and consumer expertise. A concise and descriptive title enhances discoverability and permits customers to simply establish the applying amongst others on their gadget. Traditionally, this course of has been a typical a part of Android utility growth, providing builders an easy option to current their utility’s identification to the end-user. This functionality improves consumer notion and promotes utility recognition.
The next sections will delve into the specifics of tips on how to implement this label modification, the potential issues in the course of the implementation course of, and the implications of various naming methods on consumer expertise and utility discoverability. Additional, the article will discover strategies of dealing with localization, making certain the applying title is appropriately displayed throughout completely different areas and languages.
1. String Useful resource Modification
String useful resource modification varieties the foundational factor in altering the displayed utility title on the Android working system. This course of straight influences what customers understand as the applying’s title on their units. The cause-and-effect relationship is simple: modifications to the string useful resource defining the applying title straight end in a change to the applying’s displayed title. As an example, the string useful resource named “app_name” throughout the `strings.xml` file, if initially set to “OriginalApp”, determines that “OriginalApp” is what the consumer sees. Altering this useful resource to “NewAppName” instantly modifications the displayed title to “NewAppName” upon the subsequent set up or replace. String useful resource modification’s significance stems from its function as the first mechanism via which builders can management the applying’s seen identification.
Past the fundamental performance, correct string useful resource modification necessitates consideration for localization. Functions meant for a worldwide viewers require a number of `strings.xml` information, every tailor-made to a selected language. For instance, an utility distributed in each English and Spanish may need separate `strings.xml` information, one with `My Software` and one other with `Mi Aplicacin`. With out correct localization, customers would see the default language title no matter their gadget’s locale. Additional complexity arises in managing string assets throughout completely different variations of the applying, the place names might evolve to replicate branding or characteristic updates.
In abstract, string useful resource modification is the core mechanism for controlling an Android utility’s displayed title. Whereas seemingly easy, it entails understanding localization and model management to make sure constant and applicable naming throughout various consumer bases. The problem lies in sustaining accuracy and consistency throughout a number of languages and utility variations, impacting the general consumer expertise and app discoverability.
2. Manifest File Replace
The Android Manifest file serves because the management heart for an utility, containing important metadata that defines the applying’s construction, elements, and necessities. Within the context of modifying an utility’s displayed title, a corresponding replace to the manifest file is just not straight chargeable for altering the displayed title, however slightly references the useful resource that defines it. This significant step ensures the working system appropriately identifies and shows the meant title, linking the useful resource worth to the applying.
-
`android:label` Attribute in “ Tag
The `android:label` attribute throughout the “ tag of the manifest file designates the human-readable title of the applying. It does not include the title itself; as an alternative, it factors to the string useful resource outlined within the `strings.xml` file. For instance, `android:label=”@string/app_name”` instructs the system to retrieve the applying’s title from the string useful resource named “app_name”. This indirection permits for straightforward localization, enabling the applying title to adapt to completely different languages. If the manifest file incorrectly references a non-existent or incorrect string useful resource, the applying might show an sudden title or fail to launch.
-
Dealing with Exercise-Particular Labels
Whereas the “ tag defines the default utility title, particular person “ tags can override this default. This permits builders to specify completely different names for every exercise throughout the utility, that are then displayed within the latest apps record or activity switcher. Just like the applying label, the `android:label` attribute inside an “ tag references a string useful resource. This functionality allows builders to tailor the displayed title primarily based on the exercise’s particular perform, contributing to improved consumer navigation and activity administration. An incorrect or lacking exercise label might result in consumer confusion relating to the aim of every exercise.
-
Impression on System Providers and Elements
The manifest file declaration extends past easy title show, impacting how the Android system interacts with the applying. System companies, such because the bundle supervisor, depend on the manifest file to establish and handle purposes. The appliance’s declared label, as referenced within the manifest, is used for indexing and presenting purposes in system settings and app shops. An inconsistency between the manifest declaration and the precise utility title can result in incorrect categorization and show in system-level interfaces, probably impacting utility discoverability and consumer belief.
-
Implications for Software Updates
When updating an utility, the Android system makes use of the knowledge from the manifest file to find out if any modifications have been made, together with modifications to the applying’s label. If the `android:label` attribute has been modified or if the referenced string useful resource has been up to date, the system acknowledges this variation and updates the displayed utility title accordingly after the replace is put in. Failure to correctly handle these modifications throughout an replace course of may end up in customers seeing the previous utility title even after putting in the brand new model, resulting in a poor consumer expertise.
In conclusion, the Manifest File Replace, whereas in a roundabout way storing the applying’s displayed title, is paramount for referencing the string useful resource that defines it. Incorrect or incomplete manifest file updates can disrupt the applying’s identification, impacting its visibility, discoverability, and total consumer expertise. Consequently, meticulous consideration to element throughout manifest file modification is essential for sustaining the integrity and consistency of the applying’s displayed title throughout numerous Android system elements.
3. Software Branding
Software branding serves as the method of shaping the notion of an utility out there. This contains the visible identification, messaging, and total consumer expertise. The flexibility to change the displayed utility label on Android units performs a pivotal function in straight speaking the model to the consumer, thereby influencing model recognition and app discoverability.
-
Model Id Illustration
The appliance’s displayed title is commonly the primary level of contact between a consumer and the model. A well-chosen title ought to align with the general model identification, conveying the applying’s function and values. For instance, a finance utility would possibly use a reputation suggesting stability and belief. A poorly chosen or deceptive title can injury model credibility and consumer belief. Modifications to the title permit for rebranding efforts or changes to higher replicate the applying’s evolving identification, making certain a constant model message throughout all touchpoints.
-
Market Differentiation
In a aggressive app market, a singular and memorable utility title can assist differentiate it from rivals. The flexibility to customise the displayed label offers a possibility to craft a reputation that stands out and captures the consumer’s consideration. As an example, an utility in a crowded class would possibly use a particular title to create a memorable identification. This flexibility will be essential for attracting new customers and constructing model loyalty. Strategic naming contributes considerably to establishing a definite market place.
-
Person Notion and Belief
The appliance title contributes to the consumer’s preliminary notion of the applying’s high quality and trustworthiness. An expert and related title can instill confidence and encourage customers to obtain and use the applying. Conversely, a generic or unprofessional title would possibly deter potential customers. The flexibility to refine the displayed label permits builders to optimize the title for optimum affect, making certain it resonates with the target market and fosters a optimistic consumer expertise, which is essential for long-term success.
-
Model Consistency Throughout Platforms
Sustaining a constant model identification throughout all platforms, together with Android, is crucial for constructing model recognition and loyalty. The flexibility to change the displayed utility title permits builders to make sure it aligns with the branding used on different platforms, similar to iOS or net. This consistency strengthens the general model message and avoids consumer confusion. Harmonizing the applying title throughout all channels reinforces the model’s presence and facilitates a seamless consumer expertise, strengthening model fairness.
In abstract, the method of fixing the displayed label on Android purposes is intricately linked to utility branding. The flexibility to fine-tune the displayed title affords a direct technique of speaking model values, differentiating the applying out there, fostering consumer belief, and making certain constant branding throughout numerous platforms. A well-executed naming technique is subsequently a essential part of a profitable utility launch and long-term model constructing.
4. Localization Help
The difference of an utility’s displayed title to varied languages and cultural contexts, a course of known as localization help, is inextricably linked to modifying the applying’s title on the Android platform. This adaptation extends past mere translation, encompassing cultural nuances and linguistic conventions particular to every goal locale. The efficient implementation of localization help ensures the applying’s displayed title resonates with customers worldwide, contributing to elevated adoption and improved consumer expertise.
-
Useful resource Folder Construction and Administration
Android purposes make the most of a hierarchical useful resource folder construction to handle localized content material, together with the applying’s displayed title. Every language variant is housed inside a devoted folder, denoted by language codes (e.g., “values-es” for Spanish). Inside these folders, `strings.xml` information include localized variations of the applying’s title. For instance, the default `strings.xml` within the “values” folder would possibly include `My App`, whereas the “values-fr” folder accommodates `Mon App`. Incorrect configuration of this construction, similar to lacking or incorrectly named folders, leads to the applying displaying the default language title, whatever the consumer’s gadget settings. Correct useful resource administration is essential for serving the suitable title to customers in numerous locales.
-
String Translation and Cultural Adaptation
Localization extends past direct translation. The appliance’s title should be culturally applicable and comprehensible in every goal market. A reputation that works nicely in a single language could also be nonsensical and even offensive in one other. For instance, a reputation that depends on English idioms would possibly require vital adaptation for different languages. This necessitates working with skilled translators who perceive the cultural nuances of every goal market. Failing to account for cultural sensitivities can negatively affect consumer notion and model picture. Cultural relevance is subsequently a essential part of profitable localization.
-
Runtime Language Switching
Android permits customers to modify the gadget language at runtime. Functions ought to reply dynamically to those modifications, updating the displayed title accordingly. This requires the applying to reload assets primarily based on the present gadget locale. Implementing this performance entails listening for locale modifications and refreshing the consumer interface with the suitable localized strings. Failure to help runtime language switching leads to the applying displaying the wrong title after the consumer modifications their gadget language, resulting in a disjointed consumer expertise.
-
Testing and Validation
Thorough testing is crucial to confirm the accuracy and effectiveness of localization efforts. This contains testing the applying on units with completely different language settings and validating that the displayed title is appropriately translated and culturally applicable. Automated testing instruments can help in verifying the presence and correctness of localized string assets. Neglecting localization testing may end up in essential errors going undetected, negatively impacting consumer satisfaction and probably damaging the applying’s repute in particular markets.
In conclusion, efficient localization help is just not merely a supplementary characteristic however a elementary side of modifying an utility’s displayed title for world audiences. Correct useful resource administration, culturally delicate translation, dynamic language switching, and complete testing are all integral elements of a profitable localization technique. By prioritizing these components, builders can guarantee their purposes resonate with customers throughout various linguistic and cultural backgrounds, thereby maximizing adoption and fostering optimistic consumer experiences worldwide.
5. Construct Course of Integration
The combination of utility title modification into the construct course of is a essential step for making certain consistency and accuracy throughout completely different utility variations and environments. The method entails incorporating the label change straight into the automated construct scripts or construct configuration information. This automated strategy prevents guide errors that may happen when modifying the title individually for every construct. As an example, a corporation using steady integration/steady deployment (CI/CD) pipeline might script the manipulation of `strings.xml` primarily based on the construct atmosphere (e.g., “MyApp – Dev” for growth builds, “MyApp” for manufacturing builds). This can be a cause-and-effect relationship; the construct course of dictates the applying title primarily based on predefined configurations.
Using construct variants or flavors in Android initiatives exemplifies the sensible utility of this integration. Completely different construct variants will be configured to have distinctive utility names by utilizing completely different `strings.xml` information for every variant. For instance, a “free” and “premium” model of an utility might have distinct names and bundle names, achieved solely throughout the construct course of, with out guide intervention throughout every construct. This reduces the chance of human error and maintains consistency throughout releases. The Gradle construct system, generally utilized in Android growth, offers mechanisms for injecting build-specific variables into useful resource information, permitting for dynamic title modifications primarily based on the construct configuration.
Finally, integrating title modifications into the construct course of is essential for sustaining the integrity of the applying and streamlining releases. Ignoring this integration can result in inconsistencies between environments, errors throughout deployment, and elevated guide effort. A sturdy construct course of not solely automates the title change but additionally handles localization and variant-specific configurations, leading to a dependable and environment friendly growth workflow. The adoption of those practices is important for skilled Android utility growth.
6. Testing and Validation
The method of modifying an utility’s displayed title on the Android platform necessitates rigorous testing and validation to make sure accuracy, consistency, and the absence of unintended penalties. This part is just not merely a formality however an important safeguard in opposition to potential errors that may negatively affect the consumer expertise and utility discoverability. For instance, a easy typographical error within the `strings.xml` file, if not caught throughout testing, may end up in a misspelled utility title being exhibited to customers. This straight impacts the applying’s skilled picture and might result in decreased obtain charges and adverse evaluations. Furthermore, localization errors, similar to incorrect translations of the applying title, can offend customers and create a notion of poor high quality. Thorough testing, subsequently, acts as an important filter, stopping these errors from reaching the end-user and making certain the applying presents its meant identification.
Efficient testing methods contain a number of key elements. Unit testing ought to confirm that the right string useful resource is being loaded and displayed beneath numerous situations. UI testing ought to affirm that the applying title is displayed persistently throughout all screens and contexts, together with the house display screen, app drawer, and settings menu. Localization testing should make sure that the applying title is precisely translated and culturally applicable for all supported languages. This could contain guide testing by native audio system and automatic testing instruments to detect potential points. Actual-world situations, similar to updating the applying with a modified title, must also be completely examined to make sure a clean transition and stop any knowledge loss or show errors. As an example, an utility would possibly initially show appropriately upon set up however revert to the default title after an replace because of caching points. Testing ought to establish and deal with these points earlier than they have an effect on customers.
In conclusion, testing and validation are indispensable elements of the applying title modification course of on Android. By implementing complete testing methods, builders can proactively establish and deal with potential errors, making certain the applying’s title is correct, constant, and culturally applicable. This contributes to a optimistic consumer expertise, enhances utility discoverability, and strengthens the applying’s total model picture. Neglecting this part can result in vital penalties, together with consumer dissatisfaction, adverse evaluations, and injury to the applying’s repute. Subsequently, funding in thorough testing and validation is a essential issue within the profitable deployment and upkeep of any Android utility.
7. Person Interface Consistency
Person interface consistency, pertaining to the uniform presentation and conduct of components inside an utility, assumes significance when modifying the displayed title of an Android utility. This consistency dictates that the applying’s title, as soon as modified, should be mirrored uniformly throughout all aspects of the consumer interface. Inconsistent naming can degrade the consumer expertise, probably resulting in consumer confusion and negatively impacting utility usability.
-
Software Title Show Throughout Screens
The displayed utility title ought to stay constant throughout all screens throughout the utility. This contains the title bar, settings menus, about screens, and another location the place the applying’s title is introduced. For instance, if an utility is renamed “ExampleApp,” the title needs to be “ExampleApp” persistently within the title bar of each exercise, with out reverting to an older title or displaying a variant thereof. Inconsistencies can create a way of instability or lack of polish, eroding consumer belief. Adherence to this side is paramount for sustaining knowledgeable and dependable look.
-
Launcher Icon Label Alignment
The label displayed beneath the applying’s launcher icon on the house display screen and within the app drawer should align exactly with the modified utility title. A mismatch between the launcher icon label and the applying’s inner title creates quick consumer confusion. For instance, if the applying is renamed “ProTask,” the launcher icon label should additionally show “ProTask.” Failure to take care of this alignment disrupts the consumer’s psychological mannequin of the applying and might result in misidentification or problem in finding the applying on the gadget.
-
System Integration Consistency
The appliance title as displayed within the system’s utility administration settings, share sheets, and different system-level interfaces should replicate the modified title. This integration ensures that the applying is persistently recognized all through the working system. For instance, if “PhotoEditor” is renamed to “ImagePro,” the applying’s itemizing within the system’s settings must also replicate “ImagePro.” Inconsistencies in system integration can result in problem in managing the applying or sharing content material from it, degrading the general consumer expertise.
-
Replace Course of Concerns
Throughout utility updates, the displayed title should seamlessly transition to the brand new modified title with out reverting to the previous title or displaying non permanent inconsistencies. This requires cautious administration of caching mechanisms and useful resource updates. For instance, if an utility is up to date from “Version1” to “Version2,” the displayed title ought to instantly change to “Version2” upon completion of the replace. Displaying the previous title after an replace creates confusion and requires customers to manually clear caches or restart their units, leading to a adverse notion of the applying’s high quality and reliability.
The previous aspects spotlight the interconnectedness between consumer interface consistency and modifications to an utility’s displayed title. Sustaining consistency throughout all facets of the consumer interface is essential for making certain a seamless and optimistic consumer expertise. Failure to prioritize consistency can undermine the advantages of rebranding or renaming efforts, finally impacting the applying’s success. The uniform reflection of the modified utility title throughout all system interfaces, screens, and replace processes reinforces the applying’s identification and fosters consumer belief.
8. Model Management Administration
Model management administration, a elementary follow in software program growth, performs a essential function when modifying an Android utility’s displayed title. Efficient model management ensures that modifications to the applying’s title, together with alterations to string assets and manifest information, are tracked, managed, and auditable all through the event lifecycle. The absence of sturdy model management mechanisms can result in inconsistencies, errors, and difficulties in reverting to earlier utility states.
-
Monitoring Modifications to String Sources
Model management programs, similar to Git, meticulously file all modifications to the `strings.xml` file, which accommodates the applying’s displayed title. This monitoring functionality allows builders to establish when, why, and by whom the applying title was altered. As an example, if an utility’s title is modified from “AlphaApp” to “BetaApp,” the model management system logs this variation, together with the commit message offering context. This historic file facilitates debugging and permits builders to simply revert to the earlier title if vital. With out model management, figuring out and undoing unintended title modifications turns into considerably extra complicated, probably leading to extended downtime or consumer confusion.
-
Managing Manifest File Updates
Modifications to the AndroidManifest.xml file, particularly the `android:label` attribute, are additionally tracked by model management. This ensures that modifications to the applying’s title reference within the manifest are synchronized with the corresponding modifications within the `strings.xml` file. If a developer modifies the `strings.xml` file however forgets to replace the manifest file reference, model management can spotlight this discrepancy, stopping potential runtime errors. Moreover, model management permits builders to match completely different variations of the manifest file, figuring out any unintended negative effects of the title change. This degree of scrutiny is essential for sustaining utility stability and stopping sudden conduct.
-
Branching and Merging Methods for Characteristic Improvement
When growing new options or rebranding an utility, builders typically create separate branches of their model management system. This permits them to change the applying’s title and related assets in isolation, with out affecting the primary codebase. For instance, a developer would possibly create a “rebranding” department to vary the applying’s title and visible identification. As soon as the modifications are completely examined and validated, the department will be merged again into the primary codebase. Model management programs facilitate this course of by routinely merging modifications from completely different branches, resolving any conflicts which will come up. This branched strategy ensures that title modifications are carried out in a managed and systematic method, minimizing the chance of errors and making certain a clean transition for customers.
-
Collaboration and Code Evaluate
Model management programs allow a number of builders to collaborate on the applying’s codebase concurrently. When modifying the applying’s title, builders can submit their modifications for overview by different workforce members. This code overview course of permits for scrutiny of the proposed title change, making certain that it aligns with the applying’s branding and advertising technique. Reviewers may also establish any potential points with the implementation, similar to localization errors or inconsistencies within the consumer interface. The collaborative nature of model management helps to stop errors and ensures that the applying’s title is modified in a accountable and knowledgeable method.
In abstract, model management administration is an indispensable instrument for managing modifications to an Android utility’s displayed title. By monitoring modifications to string assets, managing manifest file updates, supporting branching and merging methods, and facilitating collaboration, model management ensures that title modifications are carried out precisely, persistently, and with minimal threat. With out sturdy model management practices, builders face a considerably elevated threat of errors, inconsistencies, and difficulties in sustaining utility stability and consumer satisfaction.
Ceaselessly Requested Questions
The next addresses widespread inquiries relating to the modification of an utility’s displayed title on the Android working system. The data introduced goals to make clear procedures and deal with potential points.
Query 1: Is modification of the displayed utility title a everlasting motion?
No. The displayed utility title will be modified a number of occasions all through the applying’s lifecycle. Every modification requires an replace to the applying’s string assets and a subsequent launch to customers. Nonetheless, frequent title modifications can negatively affect consumer recognition and model identification.
Query 2: Does altering the displayed utility title have an effect on the applying’s bundle title?
No. The displayed utility title and the bundle title are distinct entities. The bundle title serves as a singular identifier for the applying throughout the Android system and shouldn’t be modified after the applying has been printed. Altering the bundle title successfully creates a brand new utility.
Query 3: Is it doable to vary the applying title with out updating the applying on the Google Play Retailer?
No. Modifications to the displayed utility title require an utility replace, which should be submitted and permitted via the Google Play Retailer. The up to date utility should then be put in by customers to replicate the title change.
Query 4: What are the potential penalties of utilizing a deceptive or inaccurate utility title?
Utilizing a deceptive or inaccurate utility title can result in consumer dissatisfaction, adverse evaluations, and potential removing of the applying from the Google Play Retailer. Adherence to Google Play Retailer insurance policies relating to correct and truthful utility descriptions is paramount.
Query 5: How does localization affect the method of fixing the applying title?
Localization requires offering translated variations of the applying title in numerous languages. This entails creating separate `strings.xml` information for every supported language and making certain that the right translation is displayed primarily based on the consumer’s gadget locale. Incomplete or inaccurate localization may end up in the applying displaying the title within the default language, regardless of the consumer’s settings.
Query 6: Can the displayed utility title be modified dynamically primarily based on consumer preferences or settings?
Whereas technically possible, dynamically altering the applying title primarily based on consumer preferences is usually not beneficial. This could create inconsistency and confusion for customers. Sustaining a constant utility title throughout all contexts is essential for model recognition and consumer expertise.
The important thing takeaway is that modifications to an utility’s displayed title require cautious planning and adherence to greatest practices to make sure a optimistic consumer expertise and compliance with platform insurance policies.
The next part will delve into superior methods for managing utility names throughout a number of construct variants and environments.
Suggestions for Altering the Displayed Software Identify on Android
Modifying the applying show title on Android requires cautious consideration to make sure a clean transition and keep a constant consumer expertise. The next ideas provide steering for managing this course of successfully.
Tip 1: Leverage Construct Variants for Setting-Particular Names
Using construct variants (flavors) permits the implementation of distinct utility names for growth, staging, and manufacturing environments. This clarifies the operational context of every construct, mitigating the chance of unintended knowledge manipulation or unintended deployment of growth variations to end-users. Every construct variant can possess its `strings.xml` file with the corresponding utility title.
Tip 2: Implement String Useful resource Localization Rigorously
Localization is essential when deploying purposes globally. Make sure that all translated `strings.xml` information include the suitable translated utility title. Make use of skilled translation companies and validate the accuracy and cultural relevance of every translation to stop consumer confusion and keep model integrity.
Tip 3: Completely Take a look at Identify Modifications on Completely different Gadgets
Take a look at the applying title modification on a wide range of Android units and OS variations. This may affirm that the title is displayed appropriately throughout completely different display screen sizes, resolutions, and system configurations. Emulators and bodily units needs to be included within the testing matrix.
Tip 4: Synchronize the Manifest File and String Sources
Assure that the `android:label` attribute within the AndroidManifest.xml file precisely references the right string useful resource in `strings.xml`. An incorrect reference will outcome within the utility displaying an unintended title, probably resulting in consumer confusion or utility launch failures.
Tip 5: Monitor Person Suggestions Put up-Replace
After releasing an utility replace with a modified title, actively monitor consumer evaluations and suggestions channels. Deal with any stories of show inconsistencies, translation errors, or adverse reactions to the title change promptly to take care of consumer satisfaction and model repute.
Tip 6: Use descriptive and brand-consistent names
Altering the show title of your utility needs to be in step with its model or be descriptive of its function. Keep away from generic names as they could hinder the purposes discoverability amongst related purposes.
Tip 7: Pay attention to character limits
When altering the show title, keep away from lengthy names. Shortening the show title permits customers to shortly establish what utility the icon they’re deciding on. Longer title will be displayed incompletely on smaller screens.
These pointers facilitate a scientific and managed strategy to modifying the displayed utility title on Android, selling consistency, accuracy, and a optimistic consumer expertise.
The following part will present a concluding abstract and ultimate suggestions.
Conclusion
The previous dialogue has completely examined the modification of an utility’s displayed title on the Android platform, a course of initiated by way of “change title of app android”. Key issues embrace meticulous string useful resource administration, exact manifest file updates, the strategic integration of branding rules, complete localization help, construct course of automation, rigorous testing and validation protocols, the upkeep of consumer interface consistency, and the diligent utility of model management practices. Every factor performs a essential function in making certain a profitable and seamless transition, contributing to consumer satisfaction and utility integrity.
The flexibility to change an utility’s displayed title presents alternatives for enhancing consumer expertise, optimizing utility discoverability, and reinforcing model identification. Nonetheless, it necessitates a disciplined and methodical strategy. The accountable execution of the practices outlined herein ensures a constant, skilled, and user-friendly expertise. Subsequently, cautious adherence to those rules is paramount for any developer in search of to successfully handle utility naming on the Android platform.
