Modifying the displayed software 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 dwelling display screen, within the app drawer, and within the software administration settings. For instance, an software internally named “ProjectPhoenix” could be displayed as “Phoenix” or “Phoenix App” to the person. This customization is achieved by means of modifications to the applying’s sources file, particularly the `strings.xml` file throughout the software’s challenge listing.
The flexibility to customise the applying’s displayed label is necessary for branding and person expertise. A concise and descriptive identify enhances discoverability and permits customers to simply establish the applying amongst others on their machine. Traditionally, this course of has been a typical a part of Android software growth, providing builders an easy option to current their software’s identification to the end-user. This functionality improves person notion and promotes software recognition.
The next sections will delve into the specifics of the best way to implement this label modification, the potential issues throughout the implementation course of, and the implications of various naming methods on person expertise and software discoverability. Additional, the article will discover strategies of dealing with localization, guaranteeing the applying title is appropriately displayed throughout totally different areas and languages.
1. String Useful resource Modification
String useful resource modification varieties the foundational component in altering the displayed software title on the Android working system. This course of instantly influences what customers understand as the applying’s identify on their gadgets. The cause-and-effect relationship is simple: modifications to the string useful resource defining the applying identify instantly lead to a change to the applying’s displayed title. For example, the string useful resource named “app_name” throughout the `strings.xml` file, if initially set to “OriginalApp”, determines that “OriginalApp” is what the person sees. Altering this useful resource to “NewAppName” instantly modifications the displayed identify to “NewAppName” upon the following set up or replace. String useful resource modification’s significance stems from its position as the first mechanism by means of which builders can management the applying’s seen identification.
Past the essential performance, correct string useful resource modification necessitates consideration for localization. Functions supposed for a worldwide viewers require a number of `strings.xml` recordsdata, every tailor-made to a particular language. For instance, an software distributed in each English and Spanish might need separate `strings.xml` recordsdata, one with `My Utility` and one other with `Mi Aplicacin`. With out correct localization, customers would see the default language identify no matter their machine’s locale. Additional complexity arises in managing string sources throughout totally different variations of the applying, the place names might evolve to replicate branding or function updates.
In abstract, string useful resource modification is the core mechanism for controlling an Android software’s displayed identify. Whereas seemingly easy, it entails understanding localization and model management to make sure constant and acceptable naming throughout various person bases. The problem lies in sustaining accuracy and consistency throughout a number of languages and software variations, impacting the general person expertise and app discoverability.
2. Manifest File Replace
The Android Manifest file serves because the management middle for an software, containing important metadata that defines the applying’s construction, parts, and necessities. Within the context of modifying an software’s displayed identify, a corresponding replace to the manifest file isn’t instantly answerable for altering the displayed identify, however quite references the useful resource that defines it. This important step ensures the working system accurately identifies and shows the supposed identify, 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 identify 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 identify from the string useful resource named “app_name”. This indirection permits for straightforward localization, enabling the applying identify to adapt to totally different languages. If the manifest file incorrectly references a non-existent or incorrect string useful resource, the applying might show an surprising identify or fail to launch.
-
Dealing with Exercise-Particular Labels
Whereas the “ tag defines the default software identify, particular person “ tags can override this default. This enables builders to specify totally different names for every exercise throughout the software, that are then displayed within the current apps checklist or process switcher. Much like the applying label, the `android:label` attribute inside an “ tag references a string useful resource. This functionality permits builders to tailor the displayed identify primarily based on the exercise’s particular perform, contributing to improved person navigation and process administration. An incorrect or lacking exercise label might result in person confusion relating to the aim of every exercise.
-
Impression on System Providers and Elements
The manifest file declaration extends past easy identify show, impacting how the Android system interacts with the applying. System companies, such because the package deal supervisor, depend on the manifest file to establish and handle purposes. The applying’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 software identify can result in incorrect categorization and show in system-level interfaces, doubtlessly impacting software discoverability and person belief.
-
Implications for Utility Updates
When updating an software, 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 modification and updates the displayed software identify 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 software identify even after putting in the brand new model, resulting in a poor person expertise.
In conclusion, the Manifest File Replace, whereas indirectly storing the applying’s displayed identify, 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 person expertise. Consequently, meticulous consideration to element throughout manifest file modification is essential for sustaining the integrity and consistency of the applying’s displayed identify throughout varied Android system parts.
3. Utility Branding
Utility branding serves as the method of shaping the notion of an software available in the market. This consists of the visible identification, messaging, and total person expertise. The flexibility to switch the displayed software label on Android gadgets performs a pivotal position in instantly speaking the model to the person, thereby influencing model recognition and app discoverability.
-
Model Id Illustration
The applying’s displayed identify is usually the primary level of contact between a person and the model. A well-chosen identify ought to align with the general model identification, conveying the applying’s function and values. For instance, a finance software may use a reputation suggesting stability and belief. A poorly chosen or deceptive identify can injury model credibility and person belief. Modifications to the identify permit for rebranding efforts or changes to raised replicate the applying’s evolving identification, guaranteeing a constant model message throughout all touchpoints.
-
Market Differentiation
In a aggressive app market, a novel and memorable software identify might help differentiate it from rivals. The flexibility to customise the displayed label offers a chance to craft a reputation that stands out and captures the person’s consideration. For example, an software in a crowded class may use a particular identify 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.
-
Consumer Notion and Belief
The applying identify contributes to the person’s preliminary notion of the applying’s high quality and trustworthiness. An expert and related identify can instill confidence and encourage customers to obtain and use the applying. Conversely, a generic or unprofessional identify may deter potential customers. The flexibility to refine the displayed label permits builders to optimize the identify for max affect, guaranteeing it resonates with the audience and fosters a constructive person expertise, which is essential for long-term success.
-
Model Consistency Throughout Platforms
Sustaining a constant model identification throughout all platforms, together with Android, is important for constructing model recognition and loyalty. The flexibility to switch the displayed software identify permits builders to make sure it aligns with the branding used on different platforms, equivalent to iOS or net. This consistency strengthens the general model message and avoids person confusion. Harmonizing the applying identify throughout all channels reinforces the model’s presence and facilitates a seamless person expertise, strengthening model fairness.
In abstract, the method of adjusting the displayed label on Android purposes is intricately linked to software branding. The flexibility to fine-tune the displayed identify gives a direct technique of speaking model values, differentiating the applying available in the market, fostering person belief, and guaranteeing constant branding throughout varied platforms. A well-executed naming technique is due to this fact a essential element of a profitable software launch and long-term model constructing.
4. Localization Assist
The difference of an software’s displayed title to numerous languages and cultural contexts, a course of known as localization assist, is inextricably linked to modifying the applying’s identify 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 assist ensures the applying’s displayed identify resonates with customers worldwide, contributing to elevated adoption and improved person 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 identify. Every language variant is housed inside a devoted folder, denoted by language codes (e.g., “values-es” for Spanish). Inside these folders, `strings.xml` recordsdata include localized variations of the applying’s identify. For instance, the default `strings.xml` within the “values” folder may include `My App`, whereas the “values-fr” folder accommodates `Mon App`. Incorrect configuration of this construction, equivalent to lacking or incorrectly named folders, leads to the applying displaying the default language identify, whatever the person’s machine 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 applying’s identify should be culturally acceptable and comprehensible in every goal market. A reputation that works effectively in a single language could also be nonsensical and even offensive in one other. For instance, a reputation that depends on English idioms may require important 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 person notion and model picture. Cultural relevance is due to this fact a essential element of profitable localization.
-
Runtime Language Switching
Android permits customers to modify the machine language at runtime. Functions ought to reply dynamically to those modifications, updating the displayed identify accordingly. This requires the applying to reload sources primarily based on the present machine locale. Implementing this performance entails listening for locale modifications and refreshing the person interface with the suitable localized strings. Failure to assist runtime language switching leads to the applying displaying the wrong identify after the person modifications their machine language, resulting in a disjointed person expertise.
-
Testing and Validation
Thorough testing is important to confirm the accuracy and effectiveness of localization efforts. This consists of testing the applying on gadgets with totally different language settings and validating that the displayed identify is accurately translated and culturally acceptable. Automated testing instruments can help in verifying the presence and correctness of localized string sources. Neglecting localization testing may end up in essential errors going undetected, negatively impacting person satisfaction and doubtlessly damaging the applying’s status in particular markets.
In conclusion, efficient localization assist isn’t merely a supplementary function however a elementary facet of modifying an software’s displayed identify for world audiences. Correct useful resource administration, culturally delicate translation, dynamic language switching, and complete testing are all integral parts 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 constructive person experiences worldwide.
5. Construct Course of Integration
The combination of software identify modification into the construct course of is a essential step for guaranteeing consistency and accuracy throughout totally different software variations and environments. The method entails incorporating the label change instantly into the automated construct scripts or construct configuration recordsdata. This automated strategy prevents handbook errors that may happen when modifying the identify individually for every construct. For example, a company using steady integration/steady deployment (CI/CD) pipeline might script the manipulation of `strings.xml` primarily based on the construct setting (e.g., “MyApp – Dev” for growth builds, “MyApp” for manufacturing builds). It is a cause-and-effect relationship; the construct course of dictates the applying identify primarily based on predefined configurations.
The usage of construct variants or flavors in Android tasks exemplifies the sensible software of this integration. Completely different construct variants will be configured to have distinctive software names by utilizing totally different `strings.xml` recordsdata for every variant. For instance, a “free” and “premium” model of an software might have distinct names and package deal names, achieved fully throughout the construct course of, with out handbook intervention throughout every construct. This reduces the danger 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 recordsdata, permitting for dynamic identify modifications primarily based on the construct configuration.
Finally, integrating identify 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 handbook effort. A sturdy construct course of not solely automates the identify 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 software growth.
6. Testing and Validation
The method of modifying an software’s displayed identify on the Android platform necessitates rigorous testing and validation to make sure accuracy, consistency, and the absence of unintended penalties. This part isn’t merely a formality however an important safeguard in opposition to potential errors that may negatively affect the person expertise and software discoverability. For instance, a easy typographical error within the `strings.xml` file, if not caught throughout testing, may end up in a misspelled software identify being exhibited to customers. This instantly impacts the applying’s skilled picture and might result in lowered obtain charges and destructive evaluations. Furthermore, localization errors, equivalent to incorrect translations of the applying identify, can offend customers and create a notion of poor high quality. Thorough testing, due to this fact, acts as an important filter, stopping these errors from reaching the end-user and guaranteeing the applying presents its supposed identification.
Efficient testing methods contain a number of key parts. Unit testing ought to confirm that the right string useful resource is being loaded and displayed beneath varied situations. UI testing ought to verify that the applying identify is displayed constantly throughout all screens and contexts, together with the house display screen, app drawer, and settings menu. Localization testing should be sure that the applying identify is precisely translated and culturally acceptable for all supported languages. This will contain handbook testing by native audio system and automatic testing instruments to detect potential points. Actual-world situations, equivalent to updating the applying with a modified identify, also needs to be totally examined to make sure a easy transition and forestall any knowledge loss or show errors. For example, an software may initially show accurately upon set up however revert to the default identify after an replace on account of caching points. Testing ought to establish and tackle these points earlier than they have an effect on customers.
In conclusion, testing and validation are indispensable parts of the applying identify modification course of on Android. By implementing complete testing methods, builders can proactively establish and tackle potential errors, guaranteeing the applying’s identify is correct, constant, and culturally acceptable. This contributes to a constructive person expertise, enhances software discoverability, and strengthens the applying’s total model picture. Neglecting this part can result in important penalties, together with person dissatisfaction, destructive evaluations, and injury to the applying’s status. Subsequently, funding in thorough testing and validation is a essential issue within the profitable deployment and upkeep of any Android software.
7. Consumer Interface Consistency
Consumer interface consistency, pertaining to the uniform presentation and habits of components inside an software, assumes significance when modifying the displayed identify of an Android software. This consistency dictates that the applying’s identify, as soon as modified, should be mirrored uniformly throughout all aspects of the person interface. Inconsistent naming can degrade the person expertise, doubtlessly resulting in person confusion and negatively impacting software usability.
-
Utility Title Show Throughout Screens
The displayed software identify ought to stay constant throughout all screens throughout the software. This consists of the title bar, settings menus, about screens, and some other location the place the applying’s identify is introduced. For instance, if an software is renamed “ExampleApp,” the title needs to be “ExampleApp” constantly within the title bar of each exercise, with out reverting to an older identify or displaying a variant thereof. Inconsistencies can create a way of instability or lack of polish, eroding person belief. Adherence to this aspect 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 software identify. A mismatch between the launcher icon label and the applying’s inside identify creates quick person 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 person’s psychological mannequin of the applying and might result in misidentification or issue in finding the applying on the machine.
-
System Integration Consistency
The applying identify as displayed within the system’s software administration settings, share sheets, and different system-level interfaces should replicate the modified identify. This integration ensures that the applying is constantly recognized all through the working system. For instance, if “PhotoEditor” is renamed to “ImagePro,” the applying’s itemizing within the system’s settings also needs to replicate “ImagePro.” Inconsistencies in system integration can result in issue in managing the applying or sharing content material from it, degrading the general person expertise.
-
Replace Course of Concerns
Throughout software updates, the displayed identify should seamlessly transition to the brand new modified identify with out reverting to the previous identify or displaying short-term inconsistencies. This requires cautious administration of caching mechanisms and useful resource updates. For instance, if an software is up to date from “Version1” to “Version2,” the displayed identify ought to instantly change to “Version2” upon completion of the replace. Displaying the previous identify after an replace creates confusion and requires customers to manually clear caches or restart their gadgets, leading to a destructive notion of the applying’s high quality and reliability.
The previous aspects spotlight the interconnectedness between person interface consistency and modifications to an software’s displayed identify. Sustaining consistency throughout all elements of the person interface is essential for guaranteeing a seamless and constructive person expertise. Failure to prioritize consistency can undermine the advantages of rebranding or renaming efforts, in the end impacting the applying’s success. The uniform reflection of the modified software identify throughout all system interfaces, screens, and replace processes reinforces the applying’s identification and fosters person belief.
8. Model Management Administration
Model management administration, a elementary observe in software program growth, performs a essential position when modifying an Android software’s displayed identify. Efficient model management ensures that modifications to the applying’s identify, together with alterations to string sources and manifest recordsdata, are tracked, managed, and auditable all through the event lifecycle. The absence of strong model management mechanisms can result in inconsistencies, errors, and difficulties in reverting to earlier software states.
-
Monitoring Adjustments to String Sources
Model management techniques, equivalent to Git, meticulously file all modifications to the `strings.xml` file, which accommodates the applying’s displayed identify. This monitoring functionality permits builders to establish when, why, and by whom the applying identify was altered. For example, if an software’s identify is modified from “AlphaApp” to “BetaApp,” the model management system logs this modification, together with the commit message offering context. This historic file facilitates debugging and permits builders to simply revert to the earlier identify if needed. With out model management, figuring out and undoing unintended identify modifications turns into considerably extra advanced, doubtlessly leading to extended downtime or person 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 identify 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 check totally different variations of the manifest file, figuring out any unintended unintended effects of the identify change. This degree of scrutiny is essential for sustaining software stability and stopping surprising habits.
-
Branching and Merging Methods for Characteristic Growth
When creating new options or rebranding an software, builders typically create separate branches of their model management system. This enables them to switch the applying’s identify and related sources in isolation, with out affecting the principle codebase. For instance, a developer may create a “rebranding” department to alter the applying’s identify and visible identification. As soon as the modifications are totally examined and validated, the department will be merged again into the principle codebase. Model management techniques facilitate this course of by mechanically merging modifications from totally different branches, resolving any conflicts which will come up. This branched strategy ensures that identify modifications are carried out in a managed and systematic method, minimizing the danger of errors and guaranteeing a easy transition for customers.
-
Collaboration and Code Overview
Model management techniques allow a number of builders to collaborate on the applying’s codebase concurrently. When modifying the applying’s identify, builders can submit their modifications for evaluate by different workforce members. This code evaluate course of permits for scrutiny of the proposed identify change, guaranteeing that it aligns with the applying’s branding and advertising technique. Reviewers may establish any potential points with the implementation, equivalent to localization errors or inconsistencies within the person interface. The collaborative nature of model management helps to stop errors and ensures that the applying’s identify is modified in a accountable and knowledgeable method.
In abstract, model management administration is an indispensable software for managing modifications to an Android software’s displayed identify. By monitoring modifications to string sources, managing manifest file updates, supporting branching and merging methods, and facilitating collaboration, model management ensures that identify modifications are carried out precisely, constantly, and with minimal threat. With out strong model management practices, builders face a considerably elevated threat of errors, inconsistencies, and difficulties in sustaining software stability and person satisfaction.
Ceaselessly Requested Questions
The next addresses frequent inquiries relating to the modification of an software’s displayed identify on the Android working system. The data introduced goals to make clear procedures and tackle potential points.
Query 1: Is modification of the displayed software identify a everlasting motion?
No. The displayed software identify will be modified a number of instances all through the applying’s lifecycle. Every modification requires an replace to the applying’s string sources and a subsequent launch to customers. Nonetheless, frequent identify modifications can negatively affect person recognition and model identification.
Query 2: Does altering the displayed software identify have an effect on the applying’s package deal identify?
No. The displayed software identify and the package deal identify are distinct entities. The package deal identify serves as a novel identifier for the applying throughout the Android system and shouldn’t be modified after the applying has been printed. Altering the package deal identify successfully creates a brand new software.
Query 3: Is it potential to alter the applying identify with out updating the applying on the Google Play Retailer?
No. Adjustments to the displayed software identify require an software replace, which should be submitted and permitted by means of the Google Play Retailer. The up to date software should then be put in by customers to replicate the identify change.
Query 4: What are the potential penalties of utilizing a deceptive or inaccurate software identify?
Utilizing a deceptive or inaccurate software identify can result in person dissatisfaction, destructive evaluations, and potential removing of the applying from the Google Play Retailer. Adherence to Google Play Retailer insurance policies relating to correct and truthful software descriptions is paramount.
Query 5: How does localization affect the method of adjusting the applying identify?
Localization requires offering translated variations of the applying identify in numerous languages. This entails creating separate `strings.xml` recordsdata for every supported language and guaranteeing that the right translation is displayed primarily based on the person’s machine locale. Incomplete or inaccurate localization may end up in the applying displaying the identify within the default language, no matter the person’s settings.
Query 6: Can the displayed software identify be modified dynamically primarily based on person preferences or settings?
Whereas technically possible, dynamically altering the applying identify primarily based on person preferences is mostly not really useful. This will create inconsistency and confusion for customers. Sustaining a constant software identify throughout all contexts is essential for model recognition and person expertise.
The important thing takeaway is that modifications to an software’s displayed identify require cautious planning and adherence to greatest practices to make sure a constructive person expertise and compliance with platform insurance policies.
The next part will delve into superior strategies for managing software names throughout a number of construct variants and environments.
Ideas for Altering the Displayed Utility Identify on Android
Modifying the applying show identify on Android requires cautious consideration to make sure a easy transition and keep a constant person 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 software names for growth, staging, and manufacturing environments. This clarifies the operational context of every construct, mitigating the danger 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 software identify.
Tip 2: Implement String Useful resource Localization Rigorously
Localization is essential when deploying purposes globally. Be sure that all translated `strings.xml` recordsdata include the suitable translated software identify. Make use of skilled translation companies and validate the accuracy and cultural relevance of every translation to stop person confusion and keep model integrity.
Tip 3: Completely Check Identify Adjustments on Completely different Gadgets
Check the applying identify modification on quite a lot of Android gadgets and OS variations. This may verify that the identify is displayed accurately throughout totally different display screen sizes, resolutions, and system configurations. Emulators and bodily gadgets 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 end result within the software displaying an unintended identify, doubtlessly resulting in person confusion or software launch failures.
Tip 5: Monitor Consumer Suggestions Put up-Replace
After releasing an software replace with a modified identify, actively monitor person evaluations and suggestions channels. Deal with any stories of show inconsistencies, translation errors, or destructive reactions to the identify change promptly to take care of person satisfaction and model status.
Tip 6: Use descriptive and brand-consistent names
Altering the show identify of your software 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 identify, keep away from lengthy names. Shortening the show identify permits customers to rapidly establish what software the icon they’re choosing. Longer identify will be displayed incompletely on smaller screens.
These tips facilitate a scientific and managed strategy to modifying the displayed software identify on Android, selling consistency, accuracy, and a constructive person expertise.
The following part will present a concluding abstract and closing suggestions.
Conclusion
The previous dialogue has totally examined the modification of an software’s displayed identify on the Android platform, a course of initiated by way of “change identify of app android”. Key issues embrace meticulous string useful resource administration, exact manifest file updates, the strategic integration of branding ideas, complete localization assist, construct course of automation, rigorous testing and validation protocols, the upkeep of person interface consistency, and the diligent software of model management practices. Every component performs a essential position in guaranteeing a profitable and seamless transition, contributing to person satisfaction and software integrity.
The flexibility to switch an software’s displayed identify presents alternatives for enhancing person expertise, optimizing software 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 ideas is paramount for any developer searching for to successfully handle software naming on the Android platform.
