Low-code platforms promise faster application delivery by reducing traditional coding. For appropriate use cases, they deliver on this promise. But platform selection requires understanding capability differences, evaluating fit for intended uses, and planning for governance.
This guide provides a framework for low-code platform evaluation.
Understanding Low-Code
What Low-Code Does
How low-code works:
Visual development: Drag-and-drop interfaces.
Pre-built components: Reusable elements.
Abstraction: Hiding underlying complexity.
Integration capability: Connecting to data and systems.
Deployment automation: Simplified delivery.
Low-Code vs. No-Code
Spectrum of less-code platforms:
No-code: No programming required; constrained capability.
Low-code: Minimal coding; more flexibility.
Pro-code enabled: Developer features in low-code platforms.
Traditional development: Full custom coding.
Use Case Fit
Where low-code works well:
Internal applications: Business tools and workflows.
Departmental apps: Line of business solutions.
Process automation: Workflow and approval applications.
Forms and data collection: Structured data capture.
Prototyping: Rapid concept validation.
Evaluation Framework
Platform Capabilities
What to assess:
Visual development: Quality of development experience.
Component library: Richness of pre-built elements.
Integration: Connectivity to systems and data.
Mobile capability: Mobile application support.
Extensibility: Custom code when needed.
Platform Categories
Major platform types:
Enterprise platforms: Mendix, OutSystems, ServiceNow.
Microsoft ecosystem: Power Platform.
Google ecosystem: AppSheet, App Engine.
Specialized: Industry or function-specific platforms.
Evaluation Approach
How to evaluate:
Requirements definition: What you need to build.
Demo evaluation: Seeing capabilities.
Proof of concept: Building with the platform.
Reference checks: Learning from others.
Total cost analysis: Full cost understanding.
Governance Considerations
Development Governance
Controlling application development:
Who can build: Developer entitlement.
What can be built: Application type governance.
How built: Standards and patterns.
Review requirements: Oversight processes.
Citizen Development
Enabling business development:
Appropriate empowerment: What's appropriate for non-IT.
Guardrails: Protecting from mistakes.
Support model: How IT assists.
Shadow IT prevention: Bringing development into visibility.
Enterprise Architecture
Platform in architecture:
Strategic fit: Where platform fits in architecture.
Integration patterns: How platform connects.
Data governance: Data access and management.
Security requirements: Security compliance.
Implementation Approach
Platform Rollout
Introducing low-code:
Pilot projects: Starting small.
Training and enablement: Building skills.
Center of Excellence: Support and governance.
Scaling: Expanding use.
Application Lifecycle
Managing low-code applications:
Development standards: How applications are built.
Deployment processes: How applications are delivered.
Maintenance: How applications are supported.
Retirement: How applications are sunset.
Common Pitfalls
Platform Selection Mistakes
Common evaluation errors:
Feature hype: Impressed by demos, not fit.
Price dominance: Lowest cost without value assessment.
Vendor positioning: Buying vendor promises.
Scope creep: Platform expected to do too much.
Implementation Mistakes
Common adoption errors:
Governance absence: Wild west citizen development.
Over-governance: Killing agility with process.
Training gaps: Users without capability.
Integration neglect: Data integration complexity.
Key Takeaways
-
Use case fit is essential: Not all applications suit low-code.
-
Governance enables scale: Without governance, chaos.
-
Total cost includes more than license: Training, support, integration.
-
Proof of concept is essential: Don't buy without building.
-
Plan for citizen development: It's coming; govern it.
Frequently Asked Questions
Which low-code platform should we choose? Depends on ecosystem, use cases, skills. Evaluate against your specific requirements.
Is low-code really faster? For appropriate use cases, yes. Not for everything.
What about vendor lock-in? Real concern. Evaluate exit strategies and data portability.
Can we build enterprise applications with low-code? Enterprise platforms support significant applications. Evaluate capability honestly.
How do we govern citizen development? Clear policies, appropriate tools, visibility, and support.
What skills do we need? Even low-code needs some developers. Also training, governance, support roles.