--- title: "No-Code Business Apps: Power Apps and Honeycode" canonical: "https://data-driven.com/blog/aws-honeycode-ms-powerapps-and-the-rise-of-no-code-business-applications/" description: "A historical look at when no-code tools fit internal business apps, how platform pricing changes the decision, and where custom code remains useful." --- Business apps · 2020 archive # Choose no-code when _the economics fit_ A historical look at when no-code tools fit internal business apps, how platform pricing changes the decision, and where custom code remains useful. 26 June 2020 3 min read Updated 25 Aug 2026 Reader brief Read it as a decision record 1. This page preserves a 2020 platform decision, not current vendor guidance. 2. User count, connectors, licensing, and support can change the answer. 3. Compare total operating cost with the value and lifespan of the app. ![AWS Honeycode interface shown in a 2020 no-code platform comparison](/_astro/Amazon_Honeycode_011.DjMAc3u__1FtQo4.webp) Dated reference This article was published on 26 June 2020. Product details, interfaces, pricing, and linked resources may have changed since then, so confirm current guidance before acting. In 2020, AWS Honeycode joined a growing group of tools for building internal applications with limited custom code. This article compared that approach with custom development and Microsoft Power Apps. The product landscape and pricing have changed since publication. The useful part of the article is the decision method: match the application, audience, integrations, lifespan, and operating model before selecting a platform. ## Where no-code can fit No-code or low-code tools can work well when: - the application serves a defined internal audience - the workflow and data model are understood - standard controls and interface patterns are acceptable - supported connectors cover the required systems - the organisation can govern makers, environments, and releases - faster initial delivery is worth an ongoing platform dependency The original article included an internal triage interface and a Teams-based workflow over a legacy system. It also described an on-demand warehouse control and a simple project tracker. ![No-code platform icons](/_astro/icon-no-code1-300x300.BHWZOzg8_1UxTsG.webp) ## Where custom development may fit better Custom code deserves consideration when: - the interface is the product - the audience is public or very large - performance or accessibility needs exceed the platform - the workflow depends on unsupported integrations - the application requires fine-grained control over deployment or data - long-term licensing changes would materially alter the business case ![Modern web application across desktop and mobile devices](/_astro/Progressive-web-app1-e1593142919423-300x278.Cgb8cqNd_3n80u.webp) This is not a claim that one approach is universally better. It is a reminder that delivery speed is only one part of the decision. ## Price the full life of the application A no-code platform can reduce initial engineering work while introducing per-user, per-app, connector, environment, or capacity costs. A custom application can cost more to build and still require ongoing hosting, maintenance, security, and support. Model at least three scenarios: 1. current users and transaction volume 2. expected growth 3. a high-use or integration-heavy case Include development, licensing, support, change, monitoring, training, and exit cost. Use current vendor terms rather than the 2020 prices that appeared in the original post. ## Treat connectors as architecture A connector can save development work, but it also defines an identity and data boundary. Confirm: - which account or workload identity the connector uses - what data it can read or change - how secrets and tokens are managed - which failures are retried - where activity is logged - who reviews new connectors A visual builder does not remove software engineering. It moves some engineering decisions into platform configuration and governance. ## Plan for product and team change The original article discussed earlier business-app tools that were later superseded. That history matters: an internal app may outlive the product version used to create it. Keep source definitions, data contracts, owners, test cases, and an export or migration plan. Train more than one person to operate the application. ## Make the choice around the workflow Choose a representative workflow and build the smallest test that exposes the hard parts: permissions, integration, exceptions, mobile use, accessibility, and lifecycle. Then compare the measured result with custom development and the organisation’s operating skills. The right answer may be low-code, custom code, or a combination of both. This archive does not retain the original vendor links or price claims. The products and commercial terms have changed since publication. Filed under - [no-code](/tag/no-code/) - [powerapps](/tag/powerapps/) Continue reading ## Related perspectives [![Business workflow moving from manual steps to Microsoft Power Automate](/_astro/Banner-image-8.ClezEc2A_Zx6ckm.webp)](/blog/turn-outdated-into-automated-the-power-of-automation-with-microsoft-power-automate/) Data Engineering ### [Microsoft Power Automate: A Practical Automation Guide](/blog/turn-outdated-into-automated-the-power-of-automation-with-microsoft-power-automate/) Identify repeatable workflows, set governance boundaries, and measure the value of Power Automate before scaling automation. [![Team planning a controlled SharePoint data-ingestion workflow](/_astro/campaign-creators-e6n7uoEnYbA-unsplash.yiyxZjdf_2vixDk.webp)](/blog/sharepoint-integration/) Data Engineering ### [SharePoint Data Ingestion with Azure Logic Apps](/blog/sharepoint-integration/) Design a SharePoint-to-Azure file workflow with controlled triggers, least-privilege access, validation, monitoring, and recovery. [![Modernizing business applications with AI and Microsoft Power Platform](/_astro/E-book_Modernize-at-scale_-with-AI-and-Microsoft_-Power-Platform.B2F159w0_1c1Lli.webp)](/blog/modernise-at-scale-with-ai-and-microsoft-power-platform/) Business ### [Modernize Apps with AI and Microsoft Power Platform](/blog/modernise-at-scale-with-ai-and-microsoft-power-platform/) Use this guide to assess Power Platform for legacy app modernization, Copilot-assisted delivery, governance, and rollout planning. ## Turn the article into a practical next step Bring the use case, constraints, and current platform. We can help you identify what to test or decide next. [Contact the team](/contact-us/) [Explore our services](/our-services/)