Low-Code Platform Vocabulary

The low-code vs no-code distinction is fundamental to selecting the right platform and communicating platform capabilities to IT governance stakeholders.

Dimension	No-code	Low-code
Target user	Business user, non-technical	Citizen developer, pro developer
Coding required	None — pure visual building	Optional — code extends visual base
Flexibility	Limited to platform capabilities	Near-unlimited via code extension
Complexity ceiling	Low–medium	Medium–high
Examples	Zapier, Airtable, Webflow	Power Apps, OutSystems, Mendix

Selection guidance:
• Choose no-code when: the builder has no technical background, the use case is well-supported by standard platform features, speed of delivery is prioritised over flexibility
• Choose low-code when: the builder has some technical aptitude, custom business logic is required, enterprise integration complexity is high, or the solution may need to evolve significantly over time

Key vocabulary:
• No-code — fully visual application development; no programming knowledge required
• Low-code — primarily visual development with code extension points
• Visual builder — the drag-and-drop interface used to compose apps and workflows without writing code
• Extension point — a defined mechanism in a low-code platform where custom code can be introduced

The citizen developer concept represents a fundamental shift in who builds software in enterprises — and understanding the role precisely is essential for IT governance and platform strategy conversations.

Citizen developer profile:
• Background: business analyst, operational specialist, finance manager, HR professional
• Motivation: needs a tool or automation to solve a departmental problem faster than the IT ticket queue allows
• Skills: deep domain knowledge + platform-specific skills (Power Apps, Zapier, Airtable)
• Scope: departmental tools, workflow automations, dashboards, simple approval processes

What distinguishes a citizen developer from an accidental technologist:
A true citizen developer operates within a governed programme:
• Uses only IT-approved platforms and connectors
• Completes mandatory platform training and certification
• Registers apps in the organisational app catalogue
• Follows data classification and privacy handling policies

Citizen developer vocabulary in context:
"We're launching a citizen developer programme on Power Platform to reduce our application development backlog by enabling business teams to build their own departmental solutions within a governed framework."

Key vocabulary:
• Citizen developer — a business user building apps on approved low-code platforms without a formal development background
• Departmental app — an application built by and for a specific business team, not IT-managed enterprise software
• Governed framework — the set of platform policies, approved connectors, and training requirements that define safe citizen development

The canvas vs model-driven choice is one of the most fundamental architectural decisions in Power Apps development — getting it wrong means rebuilding the app.

Dimension	Canvas App	Model-Driven App
UI design	Developer places controls freely	UI auto-generated from data model
Data source	Any connector (SharePoint, SQL, APIs)	Dataverse only
Best for	Custom UX, simple data model, non-Dataverse data	Complex data model, business rules, Dynamics 365 integration
Build speed	Slower for complex forms	Fast for data-centric forms and views
Flexibility	High — pixel-perfect control	Low — standard layout patterns

Decision guide:
• Canvas app when: the UX is non-standard, data comes from multiple sources outside Dataverse, the builder is working with existing SharePoint or Excel data
• Model-driven app when: the app centres on a complex Dataverse data model (contacts, cases, orders), when Dynamics 365 integration is needed, when business rules and process flows should auto-enforce on forms

Key vocabulary:
• Canvas app — a Power App designed from a blank visual canvas with full UI control
• Model-driven app — a Power App with UI automatically generated from a Dataverse data model
• Dataverse — Microsoft's relational data platform underpinning Power Platform
• Business rules — logic defined in Dataverse that enforces data validation and UI behaviour automatically

Understanding Power Automate's platform category helps position it correctly in enterprise architecture discussions and technology strategy conversations.

Power Platform component map:

Product	Category	Primary use
Power Apps	Low-code app development	Building custom applications
Power Automate	No-code/low-code workflow automation	Automating repetitive processes and approvals
Power BI	Self-service BI and analytics	Data visualisation and reporting
Power Pages	Low-code web portal builder	External-facing websites connected to Dataverse
Copilot Studio	No-code chatbot and AI agent builder	Conversational AI without machine learning expertise

Power Automate flow types:
• Cloud flows — trigger-based automations running in Azure (most common)
• Desktop flows — RPA flows automating legacy desktop UI interactions (Power Automate Desktop)
• Business process flows — guided stage-gates for business processes in model-driven apps

Key vocabulary:
• Power Automate — Microsoft's no-code/low-code workflow automation platform
• Cloud flow — an automated workflow triggered by events and running in the cloud
• RPA (Robotic Process Automation) — automation of legacy UI interactions by software robots
• Expression — a formula-like code snippet in Power Automate for data transformation (e.g. formatDateTime(utcNow(), 'dd/MM/yyyy'))

The iPaaS vs low-code distinction is important for enterprise architects making platform selection decisions — conflating them leads to choosing the wrong tool for integration-heavy use cases.

Core distinction:

Attribute	iPaaS	Low-code Platform
Primary purpose	System-to-system data integration	Building user-facing applications
Target user	Integration developer / architect	Citizen developer / app developer
Key feature	Advanced data transformation (ETL/ELT), high-volume message routing	UI builder, form designer, approval workflows
Examples	MuleSoft, Boomi, Talend, TIBCO	Power Platform, OutSystems, Mendix

The convergence challenge:
Modern platforms are blurring this boundary — Power Automate now handles significant integration scenarios, and MuleSoft now offers low-code API design. Enterprise architects must evaluate specific capabilities rather than relying on categories alone.

Decision heuristic:
• Integrating SAP ↔ Salesforce with high-volume, complex transformations → iPaaS
• Building an approval app that calls a few APIs → low-code platform
• Building a citizen developer-maintained automation that routes emails → low-code platform

Key vocabulary:
• iPaaS — Integration Platform as a Service; cloud-based middleware for system-to-system integration
• ETL/ELT — Extract, Transform, Load / Extract, Load, Transform; data integration patterns
• Message routing — directing messages between systems based on content or metadata
• Connector — a pre-built integration component for a specific service (e.g. SAP connector, Salesforce connector)