Friday, March 31, 2017

Coding for Non-Coders: 11 Smart Strategies for Successful Enterprise App Adoption

Enterprise applications are a phenomenal innovation that has changed and ameliorated the way people work. It's growing in popularity and enterprises are buying into it to make work easier, increase operational efficiency, and open new opportunities for growth.

While organizations are investing more and more in enterprise applications, there's a certain impediment to securing a return on such investments. It has actually been rocking the enterprise application industry for a while and it's a major concern for some organizations.

In our previous post in this series, we took you through the step-by-step process of building an enterprise web application for your organization. It could pass for a disservice if after showing you how to build apps, we do not show you how to deal with what is probably the biggest problem that's been hindering some organizations from getting a return on their app dev investment.

But happy are you because with this post, we've got you covered.

Okay, so what's this problem? It's failed adoption.

See, survey after survey show that user adoption is one of the biggest (if not the biggest) deterrent to high returns on enterprise application investments. In fact, in most cases, the difficult part of enterprise app initiatives isn't always the development but the deployment and adoption parts. This study conducted by SAP specifically found that 78% of enterprise applications are abandoned after their first use.

But this doesn't have to be. We believe if you plan your strategy pretty well and diligently implement it, you can achieve great success and obtain high returns on your investment in the end.

This post intends to provide you with smart strategies for successfully getting users (employees) to adopt your enterprise apps. But before we get to that, there's a basic requirement you need in place.


To start with, your app must be desirable for it to be adopted. This primarily begins with your app idea. If your idea is not worthwhile and auspicious enough, you won't be able to create great apps, which could lead to failed adoption.

So for the strategies given below to work effectively, you must first base your app on a good idea. We always recommend looking to solve real-world problems within your organization.

Employees should find your app exciting, helpful, and delightful to use. This is the first step to making an app adoptable, without which every other adoption strategy will likely fail.

After getting this out of the way, it's time to apply some smart user adoption strategies.



The truth is, people will most likely stick with what the state. So one of the first things to do is to get potential users to buy into the app early on even before you go on to build it. Let them make a commitment to using the app. For this to be effective, you will need to carry them along throughout the development process — from ideation to testing.

For one, this helps to validate your app idea. It tells if they will use the app when it's fully created or not.

Apart from being a tool for developing full-fledged apps, Joget Workflow is a great prototyping tool as well. This means it allows the end users to get involved in the app development process from the very beginning. Through an iterative cycle of change and continuous integration, end users are able to solve their current, and perhaps, anticipate future problems.


One reason employees may abandon an app is their inability to use it.

First off, you should make your app easy to use. Then make provision for the training of employees on how to use the app.

This is particularly important for complex apps with more than a handful of features and functionalities.

You should also provide helpful in-app guidance by including usage information within the app.


This one is a no-brainer. Ideally, you need to let users know where your app is so they can find it.

With Joget Workflow, users can access the apps you create from the App Center. They will only be able to see the apps they have the access permission to.

Alternatively, they can access the apps directly via a dedicated URL.

If you want ready-made Joget Workflow apps and plugins to satisfy immediate business needs, you can always get those at the Joget Marketplace.


When it comes to strategic deployment of enterprise applications, communication is key.

What exactly should you communicate? The benefits.

If you communicate the benefits of your app to prospective users, they'll want to use it. If they know it'll help them, they'll buy into it.

This is one reason why it's important for your app to have a clearly defined goal that aims at solving a real-world problem. Apparently, the more benefits your app offers, the greater your chances of getting employees to use it.


Look, employees are already using consumer apps with great qualities, and it seems they are accustomed to those apps. It's only natural for them to demand the same level of quality, simplicity, and intuitiveness in enterprise applications.

The downside is that if you don't provide them with these qualities, they will abandon your app and go back to the consumer apps they are used to. Part of your adoption plan should be to make your app as high in quality as the best ones out there.


The world is not just changing technologically, it has actually changed. The way people access information and use apps nowadays is practically different from how they used to do it a couple of years back.

Instead of traditional desktop computers, mobile is king.

Moreso, some workers these days do work on the go. Your app needs to be mobile-friendly for them to be able to use it.


Apart from your app being mobile-friendly, it ought also to be compatible with the platforms your employees use.

Since it's likely that employees may use all the major platforms, the best approach is to make the app cross-platform compatible. This means making one app available and able to run on multiple platforms. One of the benefits is that it improves your app reach while cutting down on loss in performance.

At Joget, we always advise that it's not necessary to put all the time and resources in building many different versions of the same app for different platforms. We recommend you create a web app instead. This way, the web app will be available in the cloud and can be used across multiple platforms and operating systems.

This is even more important now given the increasing trend toward bring-your-own-device (BYOD). Organizations are encouraging BYOD and employees are loving it.

Joget Workflow lets you build enterprise web applications that are mobile-optimized and crowd-ready so that your employees can use it no matter what devices they bring.


One of the quickest way to make someone start using something is to fuse that thing into their own life.

It's not different with business applications. Basically, your app shouldn't try to “refashion” the way employees work, but improve it.

Integrate your app with the tools already in use within the organization.

For example, Joget Workflow offers different plugin types for integration with systems like SharePoint, Google Apps, and Slack.


Another thing you can do to drive adoption for your app is to incentivize it. People will be more inclined to downloading and using an app if there's a valuable prize attached to it.

A great way to implement this is to start a healthy contest where the department or the individual that makes the most use of the app gets a goody reward. You may need to set up tracking to achieve this. To track, you can always add tracking mechanisms into your apps (e.g. you can embed Google Analytics).


If they don't know it exists, they won't use it. Internal promotion could range from just casual announcements at meetings to something more formal like creating bulletins or even banners.

Do whatever makes the most sense to you as an organization, but consider getting the c-level workers to use the app first. When other employees see it, they'll be encouraged to follow suit.


So you do occasionally get tech support from the services you use, huh?

Is anything wrong with providing an avenue for your app users to get the help they need internally? Of course not!

Providing internal support for your app users only goes a long way to make deployment easier and increase usage. Additionally, it'll show that you're serious about the initiative, which encourages users the more.

What to do at the help centre? Just to name a few…

It can serve as an in-house walk-in centre for getting help on how to download or use the app. This means a place for getting information
It can be a place where users easily go to leave feedback or complaints

It can be a place for fixing technical issues or walking users through technically-difficult activities


In business, there's the fallacious argument that if you build it, they will come; but of course, that's half-truth. If you build, they won't necessarily come. If you want to see results, you'd have to proactively go for it.

Enterprise app user adoption plays by the same rule — to get users to adopt your app (and to increase returns on your investment), you need to practically set out and implement strategies that work… except you have a really really awesome app that people are eager to use.

There are two parts to setting out and implementing adoption strategies: knowing the right strategies to implement, and actually implementing them.

We've done our part by providing you with information on some helpful strategies. The other part, unfortunately, we cannot do for you. It's in your hands to act accordingly.

These strategies are mostly non-technical, which means they're something you should be able to do without any technical limitations.

It's also critical to plan your adoption strategy to enhance user retention.

Feel free to have a look at the parts one, two, and three of this series or just check out the latest Joget Workflow v6 Beta for many new features and improvements in user experience (UX), mobility, app maintainability, and performance.

Friday, March 24, 2017

Coding for Non-Coders: How to Easily Build Enterprise Apps Without Coding in 8 Simple Steps

A few years ago, it wasn't entirely practicable for non-coders to build applications due to the difficulties and technicalities of coding. In fact, coding wasn't something to discuss in the average workplace except by IT.

However, technology has changed a lot of things on the app development front and it's now not just practical but also easy for non-developers to create working apps through codeless development, as we've discussed in parts one and two of this series.

Today, we will show you, in eight simple steps, exactly how to create enterprise web applications for your organization, using the Joget platform as our primary tool.

For the fact that this post targets non-technicals, we'll try to keep it free from technical jargons as much as we can while still delivering value. And where we use a technical term, we'll explain it. Let's go straight up into the steps:


Ideation is the starting point into every new project, right? Sure! So the first thing you'll need to do in creating your enterprise application is to develop an idea of what app to build.

This is where you have to define the purpose and mission of your app, its core appeal, and where it fits into the organization's overall strategy.

When it comes to ideation, you have to be very strategic, otherwise, you may end up struggling with the adoption of the app by users. Put differently, it's not just any idea that works.

For your app to carry a lot of weight with users, it should aim at solving a real-world problem for your organization. It could be efficiency problem, process problem, or just any effective organizational problem that needs solving.

Usually, these sort of problems are always almost everywhere in an organization; so you might not need to look too far. Whatever idea you arrive at, it should generally do at least one of the following:
  • Simplify complex business processes 
  • Reduce costs 
  • Save time 
  • Make employees’ jobs easier 
  • Enhance effective collaboration 
  • Allow secure access to information 
  • Resolve efficiency issues 
  • Make it possible for employees to continue working outside of the traditional office 
  • Streamline and improve workflow and approval processes 
  • Amplify opportunities for the organization 
  • And more. 
To develop even a more feasible idea, consider involving potential users (employees). Ask questions and get them to contribute ideas. Talking to prospective participants helps you validate your idea, which is important for an app to be successful.


After you've identified a need within the organization and aligned your app idea accordingly to resolve it, it's time to solidify things by properly detailing what should go into the app.

At this stage, you might want to make a list of all the major features and also research the functionalities you'd love in the app. You can brainstorm with your team and ask them what to expect.
By detailing things down, you will be able to:
  • Give your idea a structure 
  • Ensure each use case makes sense in reality 
  • Pre-design the user experience for better delivery 
  • Arrange features beforehand and map out the priority of your app’s content 
  • Connect the dots from one element to another. 
If your app is looking to resolve a problem, it's vital you find out the pain points of the prospective users so as to be able to resolve them spot on.


By now, you have your app’s use cases outlined and a mental picture of its structure. The next step is to choose an app builder platform to create your app.

Of course, we’re discussing codeless development here so the tool you choose should definitely be a no-code/low-code platform with which you can easily build apps with little or zero coding knowledge.

In our bias, we recommend Joget Workflow as your go-to development platform. It can save you tens of thousands of dollars.


With your app idea birthed, the feature set mapped out, and the functionalities defined, it’s time to further establish your project by connecting and fusing these individual pieces together.

From step #1 up to step #3, you've been preparing for the main job. Now, it's time to actually create your app. This step is probably the most technical part of this whole process, so you need to pay special attention to it.

And don't worry about the intricacies involved with development; codeless development is simple. It basically involves dragging and dropping visual elements to create what you want. Moreso, we will be using Joget Workflow, a really easy-to-use platform that makes development even enjoyable.

The first thing you would want to do in actually developing your enterprise application is to create a prototype of the app. The general idea of prototyping is to represent as close to the final product as possible, for testing.

You can use Joget Workflow to create a working and fully functioning prototype, where users can actually use the system. This way, you get the users to participate directly and they can see what they are getting from the onset.

To prototype with Joget Workflow, use the App Generator. With it, you’d be able to generate a fully functioning prototype from a form. Here’s a helpful tutorial on how to use the App Generator.

Understand that not all enterprise web applications require prototyping, especially simple and small apps. But for big apps, it's smart to create and test prototypes.

After you've created and tested a prototype of your app, and are satisfied with it, it's time to create the full application.

Creating a Joget Workflow app typically involves five simple steps as shown below:

This is the step which starts the build process.

Here, you're required to enter the details of your new app, including App ID (without spaces) and App Name.

For step-by-step instructions on designing a new app, see this tutorial.


In this step, you're to design a new form for your app using Joget's Form Builder. You will be required to enter a Form ID, Form Name, and Form Table.

Follow the instructions in this tutorial for a detailed guide on designing a form.

The third step involves designing a list using Datalist Builder.

This is where you get to create a list of cumulative field values from all workflow process instances associated with the form.
You'll need to select the source of the data, edit columns, plus a couple other functions.

Go here for details on designing a list.


Step four is where you get to design the front-end interface of your app using Userview Builder.

You can develop a theme from scratch but there's also a list of preloaded themes you can choose from for quicker development.

Here's a quick tutorial on designing a userview with Joget Workflow.

The final step in creating a Joget Workflow app centers on process design. You can complete this step using Process Builder.

For help, check out this step-by-step process of designing a process.


After you've created the full app, it's important you test it again. You will want to test the use cases, user interface, navigation, and individual screens to see if the experience is good enough.

All the components of your app should properly work at this point, and your app should be visually appealing as well.


You may find it necessary to extend the functionalities of your app. For instance, you might want to extend an account payable workflow automation app to allow vendors to submit invoices directly to the AP department.

This can be done using plugins. Joget Workflow has a robust plugin architecture you can take advantage of to enhance and extend the functionalities of your app and integrate it with external technologies such as JSON, SOAP, and SQL/JDBC.


So you now have a well-built app created and tested. Well, it's time to launch it.

App development does not end at just creating the app. It involves making sure the app gets adopted and used by the people. You wouldn't say you created a successful app if nobody is using it, would you?

We recommend you always get buy-in from potential users and other stakeholders even before creating the app. It's also intelligent to have adoption strategy.


Now that your app is in it’s fully functioning form, and with more users taking it for a spin, you may find that you need to make a couple of tweaks to bring it out fully.

Development is a process; it continues. Don't stop working on your app. Continually update and improve it based on user feedback and on new technologies.

Keep an eye on engagement. Why? Because user behavior and interaction with your app will go a long way to giving you insight into the strengths and weaknesses of your app, giving you ideas on how to improve and enhance your app.

Also, be open to constructive criticism and listen to complaints. Work with the support team of your software provider to fix technically complex problems.

Building an app can be very easy, especially with the right tools and information in hand. You don't need to be a professional coder to do so, as codeless development has totally changed the game.

We hope you try out Joget Workflow, but you ought also to try out the steps given above to build something employees will be happy to use.

This is the part three of the series, Coding for Non-Coders. Feel free to check out parts one and two if you have yet to do so.

Tuesday, March 21, 2017

Joget Workflow v6 Beta Released

After months of intensive development, we're proud to announce that the beta for Joget Workflow v6 is now available for download!

What's New in Joget Workflow v6?

v6 has a dual pronged focus: User Experience (UX), and App Maintainability and Performance.


User Experience (UX) and mobility are the Achilles' heel for enterprise apps. To address this, new features in v6 include a Material-design inspired user experience, mobile device responsiveness, dashboard capabilities and many many more.

With touch support for designing apps (imagine using an iPad to build and maintain apps!), building beautiful and user friendly apps will be easier than ever.


The major challenge in app development is not building it the first time, but rather maintaining and evolving it over time. A big focus in v6 is improving app maintainability, with additional tools to manage dependencies and to automatically merge concurrent team changes.

Performance is also another key focus area with tools to help app designers optimize their apps more easily through easy-to-use caching, and to prevent common app performance bottlenecks such as detection of database connection leaks.

Get Started

Check out all the details in What's New in Joget Workflow v6, and Get Started in the Joget Workflow v6 Knowledge Base.

Wednesday, March 8, 2017

Coding for Non-Coders: Why Should You Build Your Own Apps?

In our first post in the series, Coding for Non-Coders, we mentioned that our aim with this series is to empower non-developers to effortlessly build enterprise applications. In the post, we found that it's actually possible for a person with little or even zero coding knowledge to build applications, using a Codeless Development approach.

In part three of this series (which is the next post), we will take you through the step-by-step process of building an enterprise web application without any programming skills. But before then — and on a deep-thinking, heart-searching level — why should YOU build your own enterprise apps? Apparently, there are umpteen professional software experts out there; is it a brilliant business move to build your apps in-house in place of paying an experienced dev to do it?

Here's what we've discovered in our interactions with organizations around the world:
We've found that a good number of organizations want to create their own business-to-employee (B2E) apps. While that’s definitely a good thing, there is a problem:

The team members of these organizations, in most cases, do not know how to code. Yet, these enterprises do not necessarily want to outsource the development task; they want the apps built in-house.

Why? Because they've realized the numerous boons associated with internal development and are looking to avoid the interferential disbenefits that come with the traditional method of outsourcing app development.

The points below should help you have a clearer picture of the importance and benefits of building your own business applications internally.
  • Quicker turnaround time: One of the biggest challenges faced by organizations regarding building enterprise apps the traditional way is lengthy time requirement. On average, it takes about seven months to a year to write a single app, traditionally. Considering this extensive time input, it's worth developing your apps in-house since codeless tools can dramatically speed up the development process while saving an ample amount of time. 
  • Reduced costs: Another major reason you should build your own enterprise apps is the cost of development and maintenance. The price tag of outsourcing development is surprisingly high. On average, it costs north of $250,000 for an app to be developed. Not everyone can afford that high an amount, hence the need for internal development. With just a small fee, your team’s dream of building any app they want at any time can become a reality. 
  • Practical empowerment: In-house development empowers a broader base of your workforce — departmental people, product managers, process owners, and so on — not just IT. These non-technical team members usually have valuable domain expertise and inventive ideas, and with an opportunity to create their own apps using visual, drag-and-drop tools, they'll be able to develop their skills, make meaningful contributions, and extend their expertise to benefit the organization some more. 
  • Smart solutions to problems: Fostering a world in which everyone can build apps would not only address the traditional app backlog faced by many organizations but would also enable organizations to find new and innovative ways to *quickly* solve internal organizational problems. Think of a situation where you need to readily manage internal bookings within your organization. Can you easily and quickly create an app to handle that? Oh well, yes! But with a no-code/low-code tool like Joget Workflow
  • Trendiness: You know, the world is fast changing and work has gone from the way it used to be to a smarter approach. It's the same with development and how we use devices these days. In fact, Gartner says that before 2020, when people go online, they'll use their tablet or smartphone first instead of traditional computers. This means the demands for enterprise applications by employees is proliferating at a time when developer resources are in short supply. With this in mind, it's only intelligent you find a way to build apps internally. Gartner even mentions that by 2018, more than 50 percent of all enterprise apps will be created by business users, using codeless development tools. 
  • Increased productivity: Imagine being able to effortlessly and quickly build, at any given time, enterprise applications that can immediately enhance your team's operational efficiency and increase workers’ productivity, without the need to contact any pro developer. Now, that's the sort of benefit you get when you equip your team to build applications internally. 
  • Complete creative control: In traditional app development, there's the problem of control, customization, and versioning. Businesses that wish they could customize their app to something more custom-tailored usually have zero or very little chances of doing so given that the application wasn't written by them, and customization will most likely require coding. If they finally get to do it, such customization, versioning, and maintenance most times come with extra costs. Using no-code/low-code platforms to build your apps cuts off these unnecessary headaches and expenses while giving you complete creative control of your apps. 
The points discussed above prove it's worthwhile for organizations to build their own B2E apps. With these benefits, coupled with the simplicity of codeless development tools, creating your own apps should be something you definitely do, even as a non-coder.

You can start with Joget Workflow, one of the world's leading open source platforms for building enterprise web applications that employees love.

This is the second post in the Coding for Non-Coders series. If you haven't had any chance to read the first post, you can do so here. In part three, we'll show you exactly how to build applications with no coding requirements whatsoever.