The Color editor is part of the Manifest & resource options and is available starting with App Cloner 2.4. The option can be unlocked by purchasing the Manifest & resource options add-on.

The color editor allows replacing resource-based color definitions. Each color definition has a unique name and may reference another color definition or color selector, or it may declare a color code in hex format (#AARRGGBB), which can be previewed in the left square. Color definitions that reference color selectors cannot be previewed in the editor.

• 

• 

• 

Tapping a color definition opens the color picker where you can use a color wheel to select a replacement color. This can then be previewed in the right square. The color editor also allows entering a specific color code in hex format by switching to the Hex code tab.

Use the search button in the toolbar to search for / filter colors by name. Use the filter button to show all colors or only colors that have been edited. Additionally, you may also toggle Show referenced colors to show or hide colors that reference other colors or color selectors.

The menu item Reset allows clearing all edited colors, effectively disabling the Color editor option.

The color editor may not work with apps that use heavy resource obfuscation.

The App translator option is part of the new Manifest & resource options in App Cloner 2.3, which can be unlocked by purchasing the Manifest & resource options add-on.

Often apps are localized only for a limited number of languages. The App translator option allows you edit and translate resource strings found inside apps and thus build a new translated version of the app.

The resource strings are presented in a sorted list view. Each resource string consists of a unique key and a value. For arrays, the array index is appended to the key. For plurals, the plural identifier, e.g. zero, one, two, few, many, or other is appended.

Strings not yet translated are annotated by Needs translation in red. Translated strings are shown in green. If a string was already translated but the original string has changed, e.g. through an app update, it is annotated by Needs updated translation in orange.

Some resource strings may be used to store internal identifiers or constants, which cannot be translated or should not be modified. Long-press these strings to exclude them from the list.

Use the filter button in the toolbar to show All strings, Translated strings (this includes strings that need an updated translation), Strings needing translation (this also includes strings that need an updated translation) or Excluded strings. You can long-press an excluded string to re-include it.

The menu item Search allows you to search for / filter strings by key.

If you have the small donation, you may import or export the strings and translations using the menu items Load file and Save file. This reads or writes a CSV file with a compulsory header row containing three named columns: key, original and translated. The CSV file can be easily imported into applications such as Excel on a PC or Mac, where it may be more comfortable to translate a larger number of strings.

The menu item Reset allows clearing the translations of all strings, effectively disabling the App translator option.

Tap on a string to translate it or edit its translation.

Tap the arrow button to copy the original string into the translated string input field. Tap the share button to share the original string to other apps. For example, you can share the string directly to Google Translate to obtain a translation. Tap the copy and paste buttons to copy the original string into the clipboard and paste the clipboard into the translated string input field, respectively.

When translating strings you need to ensure that any placeholders are kept in the translation. For example, %s is a placeholder to substitute another string while %d is a placeholder to substitute a number.

There are also positional placeholders such as %1$s for a string substitution of the parameter at index 1 or %2$d for a number substitution of the parameter at index 2. Positional placeholders can be placed anywhere inside the translated string as long as they do occur at least once (they may also be used multiple times in different places). Non-positional placeholders must be kept in their original order, which means you may not swap %s with %d. App Cloner will validate all translated strings in this regard.

Cloning an app with the App translator option enabled automatically disables any other languages. This ensures that only the translated version is used, no matter what system language is configured.

The XML resource editor option is part of the new Manifest & resource options in App Cloner 2.3, which can be unlocked by purchasing the Manifest & resource options add-on. It should only be used if you are an Android developer or otherwise familiar with Android XML resource files.

Misconfiguring the app’s XML resource files could break the cloned app’s installation or cause the app to crash.

The option presents a tree view of all XML resource files found inside the app grouped by resource type, e.g. color, drawable, layout, etc. For instance, if you’re planning to modify the app’s views you would need to edit resource files under layout.

Use the search button in the toolbar to search for / filter files by filename. The menu item Search in files allows searching for strings inside the app’s XML resource files. The search operation may take some time depending on the app’s size.

The menu item Restore all files allows reverting all XML resource files to their original versions.

To edit an XML file tap on it. This will open the XML code editor.

The XML code editor offers code highlighting and also validates the XML document before returning. If you made a mistake, you can use the undo button in the toolbar to revert your changes. The undo / redo change history is only kept for the duration of the code editor session.

A search bar at the bottom allows you to find & highlight text inside the XML file.

If you have the small donation, you may import or export the XML file using the menu items Load file and Save file. The menu item Restore file allows reverting the entire file to its original version.

Note that all code editor changes are saved as patches in standard diff format. This is important in case the original app gets updated and the XML file is modified. Unless the two changes result in a conflict, e.g. a change that affects the same line, your changes will be merged with the changes from the updated app and applied to the resulting XML file. Should there be a conflict you may open the code editor and view or copy the patch file.

The Manifest editor option is part of the new Manifest & resource options in App Cloner 2.3, which can be unlocked by purchasing the Manifest & resource options add-on. It should only be used if you are an Android developer or otherwise familiar with Android manifest files.

Misconfiguring an app’s manifest could break the cloned app’s installation or cause the app to crash.

The XML code editor offers code highlighting and also validates the XML document before returning. If you made a mistake, you can use the undo button in the toolbar to revert your changes. The undo / redo change history is only kept for the duration of the code editor session.

A search bar at the bottom allows you to find & highlight text inside the XML file.

If you have the small donation, you may import or export the XML file using the menu items Load file and Save file. The menu item Restore file allows reverting the entire file to its original version.

Note that all code editor changes are saved as patches in standard diff format. This is important in case the original app gets updated and the XML file is modified. Unless the two changes result in a conflict, e.g. a change that affects the same line, your changes will be merged with the changes from the updated app and applied to the resulting XML file. Should there be a conflict you may open the code editor and view or copy the patch file.