Using the AEM Mobile Packager

When working with Adobe Experience Manager mobile, there are certain times where you need to manually create article files. We had a client ask us to fix an issue for their AEM mobile app; unfortunately, they didn’t have any source code because they were using InDesign files. We needed a way to create an article file with our own custom JavaScript and add it to the app. The AEM Mobile Packager helped solve this problem for us. The packagers sole job is to convert source code into article files. It is an easy to use tool with only a few simple steps. Here is how you use it;

First, download the zip file of the AEM mobile packager at and install it for your appropriate operating system.

On completion of the installation, a window will populate with the packager in it.

There is no need to open the application because the packager is a drag and drop tool and it will give you an error if you try to open it.

To convert your code into an article file, it must be in a folder with at least one html file named index.

If you do not have index.html, you will receive an error—and the packager will not convert your code into an article file.

CSS, JavaScript, videos, and images can be added to your folder as needed and can have different naming conventions other than index.

The last step is as simple as dragging the folder onto the packager.

The packager will create the article file, and place it next to the folder with the code. The name of the article file will be the same name as your folder.

One last thing to note is if the article file is too large, download speed and user experience are affected. It is recommended to compress any video files and convert PNG’s to JPEGs if possible. You will know if your file is too large based off the color once you upload the file on the AEM mobile portal and receive a warning message.

(green if file size is good)

(yellow or red if the article file is too large followed by a warning message)

We ran into this same issue when we were implementing the fix for the client. The image we were using was a PNG that was fairly large. When I converted it to a JPEG the download speeds improved tremendously.
The AEM Mobile Packager proved to be a useful tool based on dealing with a AEM mobile app that did not use content integration between the instance and the portal. It certainly helped us in solving our problem; please feel free to email us if you know of another way.