Your Dev Team is Spending Too Much Time on Internal Apps
February 22, 2022

Chris Smith

Internal tools — custom software built to support the business operations and used primarily by employees — are essential for managing complex internal processes that any company, from a small startup to a FAANG, relies on to operate day-to-day. Internal tools can make these processes more efficient within and between teams, and, when done right, save engineers time and resources. Retool's recent State of Internal Tools 2021 report found that developers dedicate more than 30 percent of their time to the process of internal app building.

The Big Drain on Developers' Time

While internal apps are highly valuable, build time must be taken into consideration. Internal tools can take up precious developer hours that should be spent on product development, which is the primary driver of a company's bottom line.

Survey data from the report suggests that, since the start of the pandemic, approximately 87% of developers are either spending the same amount of time or more building internal apps than they do on product development. In fact, 77 percent of surveyed companies with more than 500 employees reported having dedicated internal app teams.

What Methods Are Dev Teams Using?

To create internal apps, developers have adopted a few approaches. Developers surveyed for the report were asked which processes they typically use for building internal apps. In addition, they were asked about performance quality, user satisfaction, and loyalty (whether or not they plan to use the same method in the future) for each of those systems. We've shared their feedback here:

Custom-Built Solutions: Custom-built solutions ranked highest as the most common method for building internal apps. 81 percent of developers believe that custom-built solutions meet their needs. Nearly two in three respondents across virtually every industry stated that they use fully-customized systems, making this the most frequently utilized approach. That said, only six percent of developers that use custom-built solutions plan to continue using this method in the future.

Spreadsheet Applications: The second most common way to build internal apps is to use spreadsheet applications. However, this method garnered the lowest score for developer experience, with only 43 percent of users saying it meets their needs.

Low/No Code Platforms: Low and no code platforms ranked third in popularity with approximately 40 percent of developers identifying these systems as their preferred approach to internal app building. Within the subset of low-code users, 88 percent stated that they intend to continue using such platforms in the future, suggesting that it's highly effective.

Business Intelligence (BI) and Visualization Tools: Coming in fourth in popularity for building internal apps are BI and visualization tools. 71 percent of BI and visualization users surveyed plan to continue using this method in the future. Developers also identified and ranked their preferred tools including Tableau, PowerBI, Google Data Studio, and more.

Backend Admin Libraries: Backend admin libraries use backend frameworks as a foundation on which to build internal apps relatively easily. While they are the least common method for building internal apps, the overall sentiment around performance and user satisfaction was positive.

Unhappy Engineering Teams, Unclear Business Results

More than half of developers surveyed reported not having adequate time to complete internal app projects. Furthermore, they report that project management in internal app development is not efficient or clear. This is evident in the 33 percent of developers who stated that internal app building doesn't make a positive impact on company goals or bottom lines.

Additionally, 27 percent of developers don't have clarity on team structure in internal app projects, particularly regarding lines of ownership. These inefficiencies, communication issues, and excessive time spent building and maintaining internal apps have resulted in developers dedicating only around 70% of their time to revenue-producing work. That 70% is also inevitably impacted by stress that is carried over from developers being stretched too thin, making for unhappy developer teams.

How Can Developers Reclaim This Time?

There are pros and cons to all of the aforementioned approaches to internal app building. While most of these practices offer home-grown flexibility, they also can require significant time and resources to set up and be expensive to maintain. Developer teams should assess where home-grown vs. specialized, quick-to-implement tools make more sense to utilize. According to developers surveyed, a key issue is maintaining customizability while still making processes more efficient, and many find that low-code tools are an effective option.

As developers continue to improve upon existing processes, we'll certainly see new and even faster approaches to internal app development in the future, freeing up more developer time. This will lead to a better environment for dev teams, and internal apps with a lighter footprint on company resources.

Chris Smith is Developer Evangelist at Retool
Share this

Industry News

December 06, 2022

The Cloud Native Computing Foundation® (CNCF®), which builds sustainable ecosystems for cloud native software, announced the graduation of Argo, which will join other graduated projects such as Kubernetes, Prometheus, and Envoy.

December 06, 2022

Wib announced API PenTesting-as-a-Service (PTaaS) designed to help organizations proactively cover the latest PCI-DSS 4.0 mandates for testing application security, APIs, and vulnerabilities in Business Logic.

December 05, 2022

Harness announced Harness Cluster Orchestrator to allow customers to optimize their Kubernetes cloud workload costs and realize up to 90% cloud cost savings with Amazon Elastic Compute Cloud (Amazon EC2) Spot instances from Amazon Web Services (AWS).

December 01, 2022

Salesforce introduced a new Automation Everywhere Bundle to accelerate end-to-end workflow orchestration, automate across any system, and embed data and AI-driven workflows anywhere.

December 01, 2022

Weaveworks announced that Flux, the original GitOps project, has graduated in the Cloud Native Computing Foundation (CNCF®).

December 01, 2022

Tigera announced enhancements to its cluster mesh capabilities for managing multi-cluster environments with Calico.

December 01, 2022

CloudBees achieved the Amazon Web Service (AWS) Service Ready Program for Amazon Elastic Compute Cloud (Amazon EC2) Spot Instances.

November 30, 2022

GitLab announced the limited availability of GitLab Dedicated, a new way to use GitLab - as a single-tenant software as a service (SaaS) solution.

November 30, 2022

Red Hat announced an expansion of its open solutions publicly available in AWS Marketplace.

November 30, 2022

Sisense announced the availability of the Sisense CI/CD Git integration module.

November 29, 2022

Codenotary announced TrueSBOM for Serverless, a self-updating Software Bill of Materials (SBOM) for applications running on AWS Lamda, Google Cloud Functions and Microsoft Azure Functions that is made possible by simply adding one line to the application source code.

November 29, 2022

Code Intelligence announced its open-source Command-Line Interface (CLI) tool, CI Fuzz CLI, now allows Java developers to easily incorporate fuzz testing into their existing JUnit setup in order to find functional bugs and security vulnerabilities at scale.

November 29, 2022

Parasoft announced the 2022.2 release of Parasoft C/C++test with support for MISRA C:2012 Amendment 3 and a draft version of MISRA C++ 202x.

November 28, 2022

Kasm Technologies announced the release of Kasm Workspaces v1.12, providing major enhancements to its portfolio of digital workspaces delivering Desktop as a Service (DaaS), Virtualized Desktop Infrastructure (VDI), Remote Browser Isolation (RBI), Open-Source Intelligence Collection (OSINT), Training/Sandboxes, and Containerized Application Streaming (CAS).

November 28, 2022

Cloud4C has achieved Amazon Web Services (AWS) DevOps Competency status.