/sdcard/DroidScript/
├──
_nopremium_
├──
APKs/
│ └──
user.keystore/
├──
SPKs/
├──
Plugins/
├──
Extensions/
└──
<PROJECT_NAME>/
├──
<PROJECT_NAME>.html
├──
<PROJECT_NAME>.js
├──
build.json
├──
lang.json
├──
~<HIDDEN_FILE>
├──
Html/
├──
Snd/
├──
Misc/
└──
Img/
├──
app-icon.png
└──
If you want to allow users to switch languages, you can use the
app.SetAppLanguage method and the T() function combined with a special JSON
file called 'lang.json' in your app that looks like this:-
Also make sure you use the standard 2 letter language codes
See also: T(), GetLanguage, GetLanguageCode, GetAppLanguages, GetAppLangCode, SetAppLanguage
This file is used for signing apks. It is STRONGLY recomended that you backup this file. You cannot update your app released using this key on Google Play or on any other device, unless you have the original file (and can also remember the password!)
If you create a file called 'build.json' at the top level of your project, then you will be able to control certain aspects of the APK build process, such as the 'minSdkVersion' setting in the manifest, which sets the minimum version of Android that your app will run on.
Note: This file is optional and not required for building APKs
If you release your app on Google Play, the 'minSdkVersion' setting will control whether people with older phones can see your app in the store. If your app does not perform well on older versions of Android, then it is usually a good idea to make it unavailable for older phones or you will get lots of negative ratings and people will avoid your app. There may also be features such as Bluetooth 4.0 which are unavailable on older versions of Android.
DroidScript uses a simplified permissions model and scans your code looking for the required Android permissions, but you may want more fine-grain control of these permissions, so the 'removePermissions' setting allows you to explicitly remove Android permissions from your APK.
See the Android SDK docs for for a full list of permissions.
The 'homeScreen' setting is only used for creating home screen launchers apps, public kiosks and machine control type apps which totally take over the Android device, so don't use this option unless you know what you are doing!
If you want your app to handle certain types of file when the user tries to open them or use the 'Share via' option, then the 'pathPattern' setting allows you to specify which file types your app accepts. For example, if you were writing a text editor, then you would use the *\\.txt pattern.
See the 'Shared Data' and 'Receive Intent' samples in DroidScript for demos of how to handle file and text in your app.
The 'debuggable' setting is intended for advanced users and allows your installed app to be debugged via the Android Debug Bridge. This setting defaults to false and should never be set to true in public releases of your app.
Here is a selection of the most common used internal DroidScript assets, that are available in DroidScript and when enabling 'Include Assets' in the APK Builder.
/Sys/Img/
/Sys/Snd/
Other:
Drawable Resources:
These are not regular files but xml-based "drawable resources" provided by Android in the resources.arsc file. These two are used in some examples, but there are more: