What is AppTree IO?

The AppTree IO Platform

AppTree IO is a software platform for connecting systems and delivering user experiences. AppTree IO reduces complexity, making it simpler to create & deploy enterprise software.

Complexity in enterprise software is the enemy. It's the enemy of innovation and the enemy of software developers enjoying their work.

Thanks for joining us at AppTree in fighting this enemy. We built AppTree IO for you and appreciate your regular feedback and enthusiasm for the platform.

Here's how AppTree IO customers use the platform.

Use it for...


User Experiences

AppTree IO accelerates the delivery of point solutions using the best possible UX for the task at hand. Use AppTree to create reusable workflows and connect these to mobile, web, text, chat, and voice enabled devices. Seamlessly move between UX options, even within a single workflow.


You'll create simple workflows that automatically scale for the enterprise to synchronize transactions between systems. Use AppTree's pre-built steps to assemble your workflows and build your own using the language of your choice.

Comprehensive Applications

You can create comprehensive mobile and web apps that interact with existing enterprise systems and data, that are fast, resilient, work off-line and run natively on mobile devices.

AppTree is workflow driven

AppTree IO fights complexity with workflows.

An AppTree workflow is designed to be simple. It should do only one thing and it should do that thing to a single business transaction.

This single-purpose workflow is then made simpler by breaking it into steps. Steps perform small, incremental functions and are easily reused.

By assembling these workflows from re-usable steps, much of the work of solving a challenge is already done for you the moment you get started.

There are aspects to building enterprise workflows that are inherently complicated such as security, scalability, performance, exception handling, reading, writing an caching data. AppTree IO addresses this complexity by taking care of these for you. When you build your workflow, you only need to focus on the specific business challenge you are trying to address and let the platform assist with the enterprisification of your workflow.

You can start writing your steps right away or just create 'mock' steps and come back to them later.

AppTree's workflow architecture is designed for collaboration. You can delegate the creation of steps to other people. Each person can write their steps in the language of their choice. When they are ready, they can check them in to git. Steps can be reused by any workflows. The AppTree workflow engine can detect when a new version of a step is available and will automatically update all the workflows that use it.

AppTree IO supports any language supported by gRPC. These include Java , Swift, Python, Ruby, Node.js, Go, C#, Dart, C++

Putting the "UX" in AppTree IO

To turn your workflows into features, you will connect them to a user experience.

By user experience, we mean a mobile app, a web app or any of the other user experience options we support.

The AppTree Mobile UX clients are pre-built native mobile apps for iOS and Android. They are 100% configurable and will let you create a mobile app from your workflows without any coding. Same is true for the AppTree Web UX client.

Other UX options include devices and apps that can send text messages, email, enterprise chat tools like Slack, Teams and Mattermost, bots, voice activated devices like Alexa, Google Assistant and Siri, or even a custom app you've built yourself.

Offer your users the best UX for the point solution you are delivering. Combine UX options, even within a single transaction.

Here's an example to explain how it works.

Let's assume you created a workflow to schedule a conference room. You designed it to accept a room location, a requester, the date a room is needed and the duration. You designed it to receive the request, validate the data, get the request approved, transform it into a format your space reservation system understands and then submit it.

You put a QR code on the outside of the room to facilitate on-demand scheduling. You configured the AppTree Mobile UX client to use your workflow. When a user accesses the app, there is a menu item for 'Request Conference Room'. A user can scan the QR code to start the reservation process.

The any mobile app, the user installed it from the Apple App Store or Google Play. Or maybe you pushed it to their device from your enterprise MDM.

But maybe the user didn't install it or doesn't want to. No problem. They can just launch a web browser on their device and the same app is available on the web.

Maybe they forgot their phone today? No problem. You plugged one of those hockey-puck looking Amazon devices into the wall outlet next to the door.

"Alexa, tell Acme Corp I want to schedule this conference room..."

Once scheduled, the workflow sends the space coordinator a push notification and a text message with a request for approval. They ignore the mobile push and just open up their text messaging app. They respond Y to approve your request. Or, maybe they would prefer to check their email and click on a link in the message to approve it.

These are all just different user experiences that are talking to the same workflow. Build it once, use it everywhere.

Integrations, Integrations, Integrations...

You know that integration request you have on the back-burner that you're not too excited to get to? These steps you've been writing can be organized into integration workflows to move transactions between systems. Instead of connecting your workflow to a UX on one end, you use it to connect two systems together.

AppTree will send notifications when an automated integration fails. You tap a push notification to open the failed transaction in the mobile app and resolve the issue.

AppTree's Mobile UX Clients

AppTree supports many user experiences, however the Mobile UX clients are special.

Like all the other AppTree user experiences, you'll configure your app with YAML (secret's out, we love YAML). We've got lots of examples you can start with and it's quite readable and easy to follow. Even the most sophisticated apps with deep features are configured with a simple YAML file.

As you edit your app config file, you'll see your creation come to life on your mobile devices. You can watch it build on your Apple device, your Android, and also on the desktop, all at the same time. The experience is similar to what developers call "hot reload" where you can change something and see the results immediately without having to compile, redeploy, launch, login and navigate through the app to see your change.

When you connect your workflows to the AppTree Mobile UX clients, they are going to inherit all special capabilities we've built into them. Here are some examples of what the clients do for you...

  • Comprehensive off-line user experience

  • Insulate users from system and network outages

  • Insulate users from session disconnects

  • Reduce end-user support overhead

  • Automatic caching for large data sets

  • Dynamically improve app messaging & re-route app errors from end-users to system admins

  • Improve performance and reduce load on connected systems

  • Retrieve data and features from multiple enterprise systems in a single app experience

  • Update mobile app configuration by editing a text file

  • Native cross platform clients for iOS & Android

  • Integration with existing SSO

  • Enterprise grade security and encryption

Do you need something super advanced? Maybe you want to create a field service feature that only allows a user to clock-in to a job when they are physically at the job site? Maybe you want to auto-fill a form based on your personal preferences or physical location? Yes! you can configure features like this without any coding.

When you create a mobile app, you also are creating a web app. The same configuration file you used to define the mobile user experience is used by the AppTree Web UX client.