App Creation

Introduction

Tasker allows creation of completely standalone apps (APK files) which have no requirement for Tasker to be installed on the device they're used on.

The intention is to allow people to create their own apps for fun, for sale or just to share with friends. Or if you are concerned about all the permissions Tasker needs you can create an app that has only the permissions you require!

App creation is uncomplicated and takes only a few seconds once you're setup.

To create apps, you need the following on your device (not necessarily on the device(s) the app will run on):

Android 2.3+

Tasker App Factory (free, see below)

a device with an ARM or x86 processor (the vast majority of devices have one of those)

App creation is accessed by long-clicking on a project (not the base project) or task and selecting Export then As App. Any linked resources needed (e.g. other tasks, images) are included as part of the new app.

To export anything except a single task, you need to create a project and put anything you wish to export in the project.

Hello World Example

Let's make a simple app that just pops up Hello World! when it's launched. This example assumes that you are in Beginner Mode, please make sure that Menu / Prefs / UI / Beginner Mode is checked before you start.

1. Create A Task

make a new task

click on the Tasks tab then click + to add a new task. Give it a name Hello World.

give the task an icon

long-click on the colourful icon in the bottom right and pick any icon

add the Popup action

click + in the bottom left to add an action, select category Alert and then action Popup. Fill in Hello World! in the Text parameter, then click the accept button bottom left to accept the action, then again to accept the task.

ask Tasker to create an app

long-click on the task you just made, select Export then As App. A popup appears mentioning a Missing App.

2. Install Tasker App Factory

To generate apps, Tasker needs a free helper app called Tasker App Factory. It's available on Play Store and from the Tasker website.

Click the accept button on the popup to install the helper app.

3. App Generation

Tasker should now start generating your app, which will take maybe 12 seconds depending on your device.

If all goes well, the Cancel button will turn into an OK button meaning your app is ready!

We can't run the app straight away though because it hasn't been installed. Click on the rightmost bottom button with the Android icon to ask Android to install your app.

Once Android is done installing, you can click it's Open button to run the app, or you can simply go to the home screen and click on the app's icon in the launcher.

You should see a Hello World popup!

App Configuration

When in Beginner Mode, and if you only have one task to install, Tasker will make guesses about how to configure the resulting app.

More usually, before an app is generated you will be presented with a configuration screen which lets you specify various options for the new app.

App Signing

Android requires that all apps be signed i.e. that they certify who created them. By default, Tasker uses an automatically-generated insecure certificate to sign apps and doesn't bother mentioning it.

However, if you want to release an app via a public site (Play Store for example), you will need to sign it with a proper (secure) certificate. That's done so the site knows that it's you that's giving them the app each time you submit a new version.

Certificates are kept in a keystore which is protected with a password. To generate a keystore with a secure certificate, use Menu / More / Developer Options / Create Certificate.

Once you've generated the keystore, Tasker will often need to ask you for the certificate password before app generation so that it can be used to sign each new version of your app.

Tasker makes an automatic backup of your keystore to

/sdcard/Tasker/factory/keystore.user

when it is first created and when you backup your profile data with Menu / Data / Backup. It's highly advisable to make a copy of that file and keep it safe away from your device.

Miscellaneous

Accessibility Service

Android accessibility support changed in Android 4.1 (JellyBean). If support is needed for accessibility services in 4.1+, the Minimum Android Version in the child Configuration screen must be set to 16 or higher. If support is required pre-4.1, it must be set to less than 16.

In other words, to support both pre- and post-4.1 devices, two APKs must be generated.

This applies to all features that rely on an Accessibility Service (events Notification, New Window, Button Widget Clicked, Notification Click, variables %NTITLE, %WIN)

Google Play Store allows publication of APKs targeting different Android versions under the same package name, however this has not been tested by the developer of Tasker.

Monitor Service

Most child apps include a service which constantly monitors for events. If you know that you don't need to monitor events anymore (in-between app launches) you can use the Disable action in the Tasker category to stop it.

It will be automatically started again next time the app is launched.

Widgets / Shortcuts

it's not possible in Android to auto-create widgets with any app

it's not possible *currently* to offer the user child-app widgets, that may be available in the future to some extent

Memory Problems

If you are having low memory problems during app generation, you can ask the App Factory to use external storage for the generation process. See Menu / Prefs / More / Factory.

Preferences

The new app currently has the same default preferences as Tasker with a couple of exceptions.

You can use the Set Tasker Pref action in the Tasker category to change some of the preferences when the app is running.

Available Tasker Features

Obviously, the device the new app runs on may not have the same set of available e.g. actions as the device the app is created on.

The Test action in the Misc category allows you to check which Tasker features are available at run time (when the app is being used).

Images

Referenced images (even scene doodles and photos from the SD card) are bundled in with the app.

Plugins

When the new app is launched, it checks that all referenced plugins are installed on the device and prompts the user to install missing ones.

Some plugins may not work on other devices if they themselves store something about the action to be performed, since that data will not be available on the other device.

JavaScript actions

Scripts referenced by a JavaScript action are packaged with the new app and run directly from there.

SL4A Scripts

Scripts referenced in a Run Script action are packaged with the new app and unpacked to /sdcard/sl4a/scripts, prefixed with the package name, on first run. Tasker automatically inserts the WRITE_EXTERNAL_STORAGE permission for that purpose.

If SL4A is missing on the target device, the new app will prompt the user to download when launched.

If a new version of the app is reinstalled on the target device, the new versions of the scripts will be written if the length has changed.

Other External Components

The following external components are also checked for on launch of the new app where necessary:

Speech engines (Say, Say After)

APNDroid (Mobile Data APN)

Zoom (Zoom action category actions)

apps for 3rd Party actions

apps for 3rd Party events

Maps

The data for Maps is provided by Google and they require a maps key for each developer that uses it.

If you are using Map scene elements in your app, you will need to acquire a key from Google that can be included with your app.

0 [if necessary] setup a Google Account
0 [if necessary] create a signing keystore
0 get a fingerprint of your certificate: Menu / More / Developer Options / Certificate Checksum
0 fill in the fingerprint at Google's request page.
0 in the App Configuration screen when generating your app, enter the map key in the relevant box. The box will only be presented if your app uses one or more Map scene elements.

Variables

The new app is completely independent of Tasker, so it also does not share any variable values.

Permissions

Tasker attempts to reduce the set of permissions required by the new app to the smallest set required for the functionality it contains. For example, no Vibrate permission will be requested if there is no vibrate action used.

The WAKE_LOCK permission is unfortunately always required for technical reasons.

App Size

Generated apps are minimally around 640K but are unlikely to be significantly larger unless a lot of images are referenced. It's possible that this minimum can be reduced in the future.

Licence

You are free to distribute and sell apps created by Tasker in any way you wish. No licence fees to the developer of Tasker are necessary. It would be courteous to reference Tasker and it's website (http://tasker.dinglisch.net) somewhere in your new app if possible.

Please note that use of images from some Ipacks in commercial software is prohibited by the licence terms of the image creators. You will need to contact the image designer to request their assent in such cases. (the origin of an Ipack's images is displayed in the Ipack image selection screen).

Tasker's builtin icons are mostly from the Crystal Project, please check the licence terms on their website.