OutSystems

The market for low-code application development has skyrocketed in the last 18 months. Why? The business drivers are clear and include the increased pressure on IT teams to deliver faster solutions, the shortage of developer talent across the globe, and the increased need for business agility. At the same time, the benefits and success stories of low-code development are also making news: Doubling developer productivity, driving down total cost of ownership, and even reducing technical debt for old legacy systems.

Meet the OutSystems App Feedback feature. Specifically called out in the Gartner Magic Quadrant for Mobile Application Development Platforms 2017, this feature makes it possible for users to let you know, directly from the app, what they think or what’s causing them problems. So, let's take a look at how you can integrate App Feedback with Asana using Forge components.

Your software or app is brilliant. Everyone on your team says so. Management is over the moon. Months later, it’s basically an icon or tile sitting on a screen, ignored and idle. Users have rejected it and are either using something else or suffering in silence. What happened?

On the surface, “Low-Code” development can seem like a no-brainer for a modern organization looking for ways to digitize its business and transform its operations. The new technology promises to speed up the application development process and deliver innovative apps much quicker with better user adoption.

The drive for software and the myriad applications it offers presents a notable challenge: there are not enough professional developers to keep up with the demand for new software solutions and apps. Add to this the perennial problems of a shortage of time and money and one begins to understand the headache that is befalling many organizations across the globe.

Bill Selman is one of the leaders of the user research team at Mozilla. In this podcast he talks about how user research impacts the software development process and how that can solve some of the problems often found in bad enterprise software.

Agile has became the reference approach for modern product development in the last few decades. However, we still see a lot of misinterpretation and abuse of its core values. This is so common that there is a name for it. The experienced Agile community likes to call this unwanted byproduct frAgile. If you don’t handle it with care, it is sure to shatter your product. With this in mind, I’m going to walk you through a few examples of how Agile can indeed become frail, and how all of them are inevitably linked to frAgile anti-patterns.

What do we mean when we say enterprise software is bad? Sure, terrible hacks and technical debt could be weighing the code down. Maybe it’s a nightmare to integrate and administer. But, for most of us, it’s all about the experience of using the software. Just as today agile is pretty much everywhere, it’s now commonplace for consumer-oriented software companies to have at least one user researcher. Mozilla, the organization behind Firefox, has a team dedicated to user research and it’s led by Bill Selman. I asked Bill to tell me about the specifics of what his team works on.

Have you ever had a brilliant idea for an app only to stumble upon a reddit post where someone shares an idea similar to yours? Then, as if that weren't bad enough, the most popular comment is from someone else saying "There's an app for that"? If this sounds familiar, let me tell you a secret (spoiler alert!). There isn't always an app for that.