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 residence display, within the app drawer, and within the software administration settings. For instance, an software internally named “ProjectPhoenix” is likely to be displayed as “Phoenix” or “Phoenix App” to the consumer. This customization is achieved by way of modifications to the applying’s sources file, particularly the `strings.xml` file inside the software’s undertaking listing.
The power to customise the applying’s displayed label is vital for branding and consumer expertise. A concise and descriptive identify enhances discoverability and permits customers to simply establish the applying amongst others on their gadget. Traditionally, this course of has been a normal a part of Android software growth, providing builders an easy approach to current their software’s identification to the end-user. This functionality improves consumer notion and promotes software recognition.
The next sections will delve into the specifics of the best way to implement this label modification, the potential concerns throughout the implementation course of, and the implications of various naming methods on consumer expertise and software 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 types the foundational component in altering the displayed software title on the Android working system. This course of straight influences what customers understand as the applying’s identify on their units. The cause-and-effect relationship is simple: modifications to the string useful resource defining the applying identify straight end in a change to the applying’s displayed title. For example, the string useful resource named “app_name” inside 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 identify to “NewAppName” upon the following set up or replace. String useful resource modification’s significance stems from its function as the first mechanism by way of which builders can management the applying’s seen identification.
Past the fundamental performance, correct string useful resource modification necessitates consideration for localization. Purposes supposed for a world viewers require a number of `strings.xml` information, every tailor-made to a particular language. For instance, an software distributed in each English and Spanish may need separate `strings.xml` information, one with `My Utility` and one other with `Mi Aplicacin`. With out correct localization, customers would see the default language identify no matter their gadget’s locale. Additional complexity arises in managing string sources throughout completely different variations of the applying, the place names could evolve to mirror 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 consumer bases. The problem lies in sustaining accuracy and consistency throughout a number of languages and software variations, impacting the general consumer expertise and app discoverability.
2. Manifest File Replace
The Android Manifest file serves because the management heart for an software, containing important metadata that defines the applying’s construction, elements, and necessities. Within the context of modifying an software’s displayed identify, a corresponding replace to the manifest file will not be straight liable for altering the displayed identify, however quite references the useful resource that defines it. This significant 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 inside 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 completely different languages. If the manifest file incorrectly references a non-existent or incorrect string useful resource, the applying could 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 permits builders to specify completely different names for every exercise inside the software, that are then displayed within the current apps listing or job switcher. Much like the applying label, the `android:label` attribute inside an “ tag references a string useful resource. This functionality allows builders to tailor the displayed identify primarily based on the exercise’s particular perform, contributing to improved consumer navigation and job administration. An incorrect or lacking exercise label could result in consumer confusion relating to the aim of every exercise.
-
Impression on System Companies and Elements
The manifest file declaration extends past easy identify show, impacting how the Android system interacts with the applying. System providers, such because the package deal supervisor, depend on the manifest file to establish and handle functions. The applying’s declared label, as referenced within the manifest, is used for indexing and presenting functions 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 consumer belief.
-
Implications for Utility Updates
When updating an software, the Android system makes use of the data 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 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 consumer expertise.
In conclusion, the Manifest File Replace, whereas in a roundabout way 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 general consumer 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 elements.
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 general consumer expertise. The power to change the displayed software label on Android units performs a pivotal function in straight speaking the model to the consumer, thereby influencing model recognition and app discoverability.
-
Model Identification Illustration
The applying’s displayed identify is commonly the primary level of contact between a consumer and the model. A well-chosen identify ought to align with the general model identification, conveying the applying’s objective and values. For instance, a finance software may use a reputation suggesting stability and belief. A poorly chosen or deceptive identify can harm model credibility and consumer belief. Modifications to the identify enable for rebranding efforts or changes to higher mirror 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 software identify will help differentiate it from rivals. The power to customise the displayed label supplies a possibility to craft a reputation that stands out and captures the consumer’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.
-
Person Notion and Belief
The applying identify contributes to the consumer’s preliminary notion of the applying’s high quality and trustworthiness. Knowledgeable 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 power to refine the displayed label permits builders to optimize the identify for max affect, making certain it resonates with the audience 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 power to change the displayed software identify permits builders to make sure it aligns with the branding used on different platforms, resembling iOS or net. This consistency strengthens the general model message and avoids consumer confusion. Harmonizing the applying identify 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 functions is intricately linked to software branding. The power to fine-tune the displayed identify provides a direct technique of speaking model values, differentiating the applying available in the market, fostering consumer belief, and making certain constant branding throughout varied platforms. A well-executed naming technique is due to this fact a crucial element of a profitable software launch and long-term model constructing.
4. Localization Assist
The variation of an software’s displayed title to numerous languages and cultural contexts, a course of known as localization help, 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 help ensures the applying’s displayed identify resonates with customers worldwide, contributing to elevated adoption and improved consumer expertise.
-
Useful resource Folder Construction and Administration
Android functions 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` information 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 incorporates `Mon App`. Incorrect configuration of this construction, resembling lacking or incorrectly named folders, ends in the applying displaying the default language identify, 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 applying’s identify have to 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 consumer notion and model picture. Cultural relevance is due to this fact a crucial element of profitable localization.
-
Runtime Language Switching
Android permits customers to modify the gadget language at runtime. Purposes ought to reply dynamically to those modifications, updating the displayed identify accordingly. This requires the applying to reload sources 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 ends in the applying displaying the inaccurate identify 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 consists of testing the applying on units with completely 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 crucial errors going undetected, negatively impacting consumer satisfaction and doubtlessly damaging the applying’s repute in particular markets.
In conclusion, efficient localization help will not be merely a supplementary function however a basic side 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 elements of a profitable localization technique. By prioritizing these parts, builders can guarantee their functions 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 software identify modification into the construct course of is a crucial step for making certain consistency and accuracy throughout completely different software variations and environments. The method entails incorporating the label change straight into the automated construct scripts or construct configuration information. This automated method prevents handbook errors that may happen when modifying the identify individually for every construct. For example, a corporation using steady integration/steady deployment (CI/CD) pipeline could 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 identify primarily based on predefined configurations.
The usage of construct variants or flavors in Android initiatives exemplifies the sensible software of this integration. Totally different construct variants will be configured to have distinctive software names through the use of completely different `strings.xml` information for every variant. For instance, a “free” and “premium” model of an software could have distinct names and package deal names, achieved totally inside 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, supplies mechanisms for injecting build-specific variables into useful resource information, permitting for dynamic identify modifications primarily based on the construct configuration.
In the end, 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 strong construct course of not solely automates the identify change but in addition 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 section will not be merely a formality however a necessary safeguard towards potential errors that may negatively affect the consumer 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 straight impacts the applying’s skilled picture and might result in decreased obtain charges and unfavourable evaluations. Furthermore, localization errors, resembling 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 a vital filter, stopping these errors from reaching the end-user and making certain the applying presents its supposed 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 underneath varied situations. UI testing ought to affirm that the applying identify is displayed constantly throughout all screens and contexts, together with the house display, 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, resembling updating the applying with a modified identify, also needs to be completely examined to make sure a easy transition and forestall any information loss or show errors. For example, an software may initially show accurately upon set up however revert to the default identify after an replace resulting from 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 elements of the applying identify modification course of on Android. By implementing complete testing methods, builders can proactively establish and tackle potential errors, making certain the applying’s identify is correct, constant, and culturally acceptable. This contributes to a optimistic consumer expertise, enhances software discoverability, and strengthens the applying’s general model picture. Neglecting this section can result in important penalties, together with consumer dissatisfaction, unfavourable evaluations, and harm to the applying’s repute. Due to this fact, funding in thorough testing and validation is a crucial issue within the profitable deployment and upkeep of any Android software.
7. Person Interface Consistency
Person interface consistency, pertaining to the uniform presentation and conduct of parts 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, have to be mirrored uniformly throughout all aspects of the consumer interface. Inconsistent naming can degrade the consumer expertise, doubtlessly resulting in consumer confusion and negatively impacting software usability.
-
Utility Title Show Throughout Screens
The displayed software identify ought to stay constant throughout all screens inside 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 ought 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 consumer belief. Adherence to this aspect is paramount for sustaining an expert and dependable look.
-
Launcher Icon Label Alignment
The label displayed beneath the applying’s launcher icon on the house display 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 rapid consumer confusion. For instance, if the applying is renamed “ProTask,” the launcher icon label should additionally show “ProTask.” Failure to keep up this alignment disrupts the consumer’s psychological mannequin of the applying and might result in misidentification or issue in finding the applying on the gadget.
-
System Integration Consistency
The applying identify as displayed within the system’s software administration settings, share sheets, and different system-level interfaces should mirror 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 mirror “ImagePro.” Inconsistencies in system integration can result in issue in managing the applying or sharing content material from it, degrading the general consumer expertise.
-
Replace Course of Issues
Throughout software updates, the displayed identify should seamlessly transition to the brand new modified identify with out reverting to the previous identify or displaying non permanent 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 units, leading to a unfavourable notion of the applying’s high quality and reliability.
The previous aspects spotlight the interconnectedness between consumer interface consistency and modifications to an software’s displayed identify. Sustaining consistency throughout all facets of the consumer interface is crucial 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 software identify 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 basic observe in software program growth, performs a crucial function 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 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 software states.
-
Monitoring Modifications to String Assets
Model management programs, resembling Git, meticulously report all modifications to the `strings.xml` file, which incorporates the applying’s displayed identify. This monitoring functionality allows 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 variation, together with the commit message offering context. This historic report facilitates debugging and permits builders to simply revert to the earlier identify if vital. With out model management, figuring out and undoing unintended identify modifications turns into considerably extra advanced, doubtlessly 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 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 match completely different variations of the manifest file, figuring out any unintended unwanted side effects of the identify change. This degree of scrutiny is essential for sustaining software stability and stopping surprising conduct.
-
Branching and Merging Methods for Function Growth
When creating new options or rebranding an software, builders usually create separate branches of their model management system. This permits them to change 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 completely examined and validated, the department will be merged again into the principle 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 method ensures that identify modifications are applied in a managed and systematic method, minimizing the danger of errors and making certain a easy transition for customers.
-
Collaboration and Code Evaluation
Model management programs 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 assessment by different staff members. This code assessment course of permits for scrutiny of the proposed identify change, making certain that it aligns with the applying’s branding and advertising technique. Reviewers can even establish any potential points with the implementation, resembling localization errors or inconsistencies within the consumer interface. The collaborative nature of model management helps to forestall errors and ensures that the applying’s identify is modified in a accountable and knowledgeable method.
In abstract, model management administration is an indispensable device 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 applied precisely, constantly, and with minimal threat. With out sturdy model management practices, builders face a considerably elevated threat of errors, inconsistencies, and difficulties in sustaining software stability and consumer satisfaction.
Steadily Requested Questions
The next addresses widespread 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 consumer 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 singular identifier for the applying inside 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. Modifications to the displayed software identify require an software replace, which have to be submitted and accredited by way of the Google Play Retailer. The up to date software should then be put in by customers to mirror 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 consumer dissatisfaction, unfavourable 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 fixing the applying identify?
Localization requires offering translated variations of the applying identify 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 identify within the default language, regardless of the consumer’s settings.
Query 6: Can the displayed software identify be modified dynamically primarily based on consumer preferences or settings?
Whereas technically possible, dynamically altering the applying identify primarily based on consumer preferences is mostly not really helpful. This will create inconsistency and confusion for customers. Sustaining a constant software identify throughout all contexts is essential for model recognition and consumer expertise.
The important thing takeaway is that modifications to an software’s displayed identify require cautious planning and adherence to finest practices to make sure a optimistic consumer 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 preserve a constant consumer expertise. The next suggestions supply 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 information manipulation or unintentional 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 crucial when deploying functions globally. Be sure that all translated `strings.xml` information include the suitable translated software identify. Make use of skilled translation providers and validate the accuracy and cultural relevance of every translation to forestall consumer confusion and preserve model integrity.
Tip 3: Completely Take a look at Identify Modifications on Totally different Units
Take a look at the applying identify modification on quite a lot of Android units and OS variations. It will affirm that the identify is displayed accurately throughout completely different display sizes, resolutions, and system configurations. Emulators and bodily units ought to be included within the testing matrix.
Tip 4: Synchronize the Manifest File and String Assets
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 software displaying an unintended identify, doubtlessly resulting in consumer confusion or software launch failures.
Tip 5: Monitor Person Suggestions Submit-Replace
After releasing an software replace with a modified identify, actively monitor consumer evaluations and suggestions channels. Deal with any stories of show inconsistencies, translation errors, or unfavourable reactions to the identify change promptly to keep up consumer satisfaction and model repute.
Tip 6: Use descriptive and brand-consistent names
Altering the show identify of your software ought to be in line with its model or be descriptive of its objective. Keep away from generic names as they could hinder the functions discoverability amongst related functions.
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 deciding on. Longer identify will be displayed incompletely on smaller screens.
These tips facilitate a scientific and managed method to modifying the displayed software identify on Android, selling consistency, accuracy, and a optimistic consumer expertise.
The next part will present a concluding abstract and last suggestions.
Conclusion
The previous dialogue has completely examined the modification of an software’s displayed identify on the Android platform, a course of initiated through “change identify of app android”. Key concerns embody meticulous string useful resource administration, exact manifest file updates, the strategic integration of branding ideas, complete localization help, construct course of automation, rigorous testing and validation protocols, the upkeep of consumer interface consistency, and the diligent software of model management practices. Every component performs a crucial function in making certain a profitable and seamless transition, contributing to consumer satisfaction and software integrity.
The power to change an software’s displayed identify presents alternatives for enhancing consumer expertise, optimizing software discoverability, and reinforcing model identification. Nonetheless, it necessitates a disciplined and methodical method. The accountable execution of the practices outlined herein ensures a constant, skilled, and user-friendly expertise. Due to this fact, cautious adherence to those ideas is paramount for any developer in search of to successfully handle software naming on the Android platform.
