Spec Driven Development
with Lianja 14
A Better Way to Build AI-Ready Business Applications
Updated: June 2026
AI-assisted development is most powerful when the AI understands exactly what the application is meant to do. A vague prompt can produce a useful suggestion, but a clear functional specification can guide design, analytics, workflow, validation and implementation with far more consistency.
That is the idea behind Spec Driven Development in Lianja 14. Instead of treating AI as a one-off coding assistant, Lianja 14 lets teams use the Lianja AI Assistant Instructions feature to capture functional specifications that can be reused, selected and applied as part of the development experience.
The result is a more structured way to build modern business applications. The specification becomes a working asset, not just a document. It tells the AI Assistant what the application is, what the business rules are, what the users need, how the data should be interpreted and how conversational analytics should behave.
For serious business database applications, that matters. The value of AI is not only in generating code. It is in helping teams move from business intent to working software while keeping the application grounded in agreed requirements.
Why Spec Driven Development Matters
Traditional development often starts with a written requirement, then moves into design, coding, testing and revision. AI-assisted development can accelerate that process, but only when the AI is given enough context to make good decisions.
Without a clear spec, AI output can drift. It may answer the immediate prompt but miss the larger business process. It may use the wrong terminology, make assumptions about the data, overlook validation rules or generate a workflow that looks plausible but does not match how the organization actually works.
Spec Driven Development solves this by putting the functional specification at the center of the AI interaction. The AI Assistant is not working from isolated prompts. It is working from named instructions that describe the business purpose, expected behavior and application context.
That makes the development process more repeatable, more transparent and easier to refine over time.
How Lianja 14 Uses AI Assistant Instructions
In Lianja 14, the Lianja AI Assistant Instructions feature can be used to write and manage functional specs. These instructions provide persistent guidance to the AI Assistant, allowing the spec to become part of the development workflow rather than something that sits outside the application lifecycle.
Instructions can define the expected behavior of an application, a module, a workflow or a conversational analytics experience. They can describe the data model, business vocabulary, calculations, permissions, validation rules, reporting needs and acceptance criteria that the AI Assistant should observe when helping the developer or business user.
This is a practical shift. The spec becomes something the AI Assistant can actively use.
Where Instructions Are Stored
Lianja 14 stores AI Assistant Instructions according to the current workspace context.
- If the user is in the Data workspace and a database container is open, Instructions live in that database container.
- This allows Instructions to be used to spec conversational analytics against the database context.
- If there is no open database container in the Data workspace, Instructions are stored as
.spec files.
- Those
.spec files are stored under lib:/aiassistant/instructions/<username>.
- Each spec file can have spaces in its display name, with spaces converted to underscores when the file is saved.
- This allows the spec to be displayed cleanly in the Instructions selection combo.
This storage model is important because it makes the spec reusable. A functional specification can be selected again, refined, reused for related work and applied consistently inside the AI-assisted development process.
From Prompting to Spec Driven Development
Prompting is useful, but prompts are often temporary. A developer asks a question, gets an answer and moves on. The next prompt may not include the same assumptions, business vocabulary or rules. Over time, context can become fragmented.
Spec Driven Development is different. The team creates a functional spec first, then uses that spec to guide the AI Assistant. The instructions become a stable reference point for the application.
| Requirement | Ad-hoc AI prompting | Lianja 14 Spec Driven Development |
|---|
| Starting point |
A single prompt or short request |
A functional spec written as AI Assistant Instructions |
| Business context |
Repeated manually in each conversation |
Captured once and reused through named instructions |
| Analytics behavior |
Depends on the wording of each question |
Can be guided by specs linked to the data workspace or database container |
| Reuse |
Often copy and paste |
Selected from the Instructions combo |
| Storage |
Usually hidden inside a chat history |
Stored in a database container or as .spec files |
| Consistency |
Can vary from prompt to prompt |
Anchored by a persistent functional specification |
| Application lifecycle |
Separate from the development asset base |
Part of the AI-assisted application workflow |
Writing the Functional Spec
A good functional spec for the Lianja AI Assistant should be clear enough for both people and AI. It should describe what the application needs to do, but also how the business thinks about the problem.
Useful areas to include are:
- The business purpose of the application or module.
- The users, roles and permissions involved.
- The data entities, relationships and important fields.
- The workflows users need to complete.
- The validation rules and business constraints.
- The reports, dashboards or conversational analytics the application should support.
- The terminology the AI Assistant should use when talking about the data.
- The expected outputs, acceptance criteria and edge cases.
This gives the AI Assistant a much better foundation. Instead of guessing what the application should mean, it can work from the specification the team has already agreed on.
Spec Driven Conversational Analytics
One of the most important uses for Instructions in Lianja 14 is conversational analytics. Business users increasingly want to ask questions about data in natural language, but useful analytics require more than access to tables and fields.
The AI needs to understand the business meaning of the data. It needs to know which measures matter, how terms should be interpreted, which filters are expected, what calculations are valid and what kind of answers are useful to the user.
When Instructions live in an open database container in the Data workspace, they can be used to spec conversational analytics in context. That means the specification can describe how questions should be interpreted against the database, making analytics more aligned with the actual business domain.
For example, a spec can define:
- What a customer, order, invoice, case or project means in the application.
- Which fields should be used for common analytics questions.
- How date ranges, status values and totals should be interpreted.
- Which questions should respect user roles or data visibility rules.
- How answers should be phrased for business users.
This is where Spec Driven Development becomes especially powerful. It allows conversational analytics to be shaped by the business specification, not just by the raw database structure.
Why This Fits Lianja
Lianja has always been focused on building serious data-centric business applications. Lianja 14 extends that direction by making AI assistance more structured and more closely connected to the application development process.
Spec Driven Development fits naturally with Lianja because business applications are full of rules, workflows, data relationships and role-specific behavior. Those details need to be captured somewhere. With Lianja AI Assistant Instructions, they can be captured in a form the AI Assistant can actually use.
That helps no-code, low-code and pro-code teams work from the same intent. Business users can describe what is needed. Developers can refine the spec into implementation detail. The AI Assistant can help generate, explain, analyze and improve the application with a stronger understanding of the desired outcome.
A Full End-to-End Platform for Business Solutions
Lianja's approach to Spec Driven Development is powerful because it sits inside a complete application platform, not beside one. Lianja brings together Lianja Studio, Lianja Cloud Server, Lianja App Center, Lianja Apps Cloud and Premium Support so teams can design, build, deploy, secure and support business solutions from one environment.
That matters for business AI. A generated screen, workflow or script is only useful if the resulting solution remains editable, supportable and secure. Lianja keeps AI-assisted work connected to the application model, database, permissions, deployment path and runtime platform.
When the functional spec captures users, roles, data visibility, validation rules, workflows and reporting behavior, it guides more than code suggestions. It helps teams create business solutions that can be maintained, administered and evolved over time instead of producing one-off AI output that is difficult to govern.
See the Lianja overview for the broader platform picture.
Better Specs, Better Applications
The quality of an AI-assisted application depends heavily on the quality of the context given to the AI. A weak prompt produces a weak starting point. A strong functional spec gives the AI Assistant a much better foundation.
With Lianja 14, the spec is not just an external planning document. It can be stored, selected and reused as part of the AI Assistant workflow. That helps teams avoid repeated explanations, reduce ambiguity and keep development aligned with business intent.
It also encourages a better discipline: describe the application before asking AI to help build it.
The Bottom Line
Spec Driven Development with Lianja 14 is a practical way to bring structure to AI-assisted application development.
By using Lianja AI Assistant Instructions to write functional specs, teams can make AI guidance more consistent, reusable and business-aware. Instructions can live in a database container when working in the Data workspace with an open database container, making them useful for conversational analytics. Otherwise, they are stored as .spec files under lib:/aiassistant/instructions/<username>, with spaces converted to underscores on saving so the specs can be displayed in the Instructions selection combo.
For business applications, that is a strong model. The spec becomes the bridge between business intent and AI-assisted delivery. Because Lianja is a full end-to-end platform, that delivery can remain secure, editable and supportable as the solution evolves.
Copyright © 2026 Lianja Inc. All rights reserved worldwide. Lianja™, Lianja Studio™, Lianja Cloud Server™, Lianja App Center™ and No-Code™ are trademarks of Lianja Inc.
|
|
What Lianja Products Do I Need?
Flexible licensing options for Desktop, Web, Mobile and Cloud deployment.
Lianja provides simple subscription options based on how you want to build, deploy and scale your business applications.
Updated: June 2026
Here’s What You Need
The right Lianja subscription depends on your deployment model. Some teams only need to build and distribute Desktop applications. Others need to deploy Web and Mobile applications on their own infrastructure, or use a fully managed cloud environment.
1. Building and Deploying Desktop Applications
For developing and deploying Desktop Applications, all you need is Lianja Studio. Lianja Studio is the visual development environment for building Desktop, Web and Mobile business applications on Windows, macOS and Linux.
Desktop applications built with Lianja Studio can be distributed without additional desktop runtime licensing fees while your subscription is active. This makes Lianja Studio a cost-effective choice for developers, ISVs and businesses that need to build and distribute desktop business applications.
- One developer license for Windows, macOS and Linux.
- Up to 3 activations for the same developer.
- Unlimited Desktop App distribution while your subscription is active.
- Lianja App Center for secure app access, provisioning and user management.
- Cloud Server development tools for testing Web and Mobile applications before production deployment.
2. Deploying Web and Mobile Applications
If you want to deploy Web and Mobile applications, you have two primary options:
- Self-host with Lianja Cloud Server on your own servers, private cloud or public cloud infrastructure.
- Use Lianja Apps Cloud for managed hosting without maintaining your own application server infrastructure.
a) Self-Hosting with Lianja Cloud Server
For organizations that prefer to self-host their Web and Mobile applications, Lianja Cloud Server provides a secure deployment environment for applications built with Lianja Studio.
Lianja Cloud Server can be installed on Windows Server or Linux, and can run on your own servers, private cloud infrastructure or public cloud platforms such as AWS, Azure and Google Cloud.
Standard Edition
- Concurrent Connections: Supports up to 250 concurrent cloud connections, suitable for approximately 50 users.
- Platform: Available for Windows Server or Linux.
- Included Features: Web Client and Mobile Client frameworks, OData REST APIs and standard support.
- Pricing: US$995 per year.
Professional Edition
- Concurrent Connections: Supports unlimited concurrent cloud connections for larger user bases.
- Platform: Available for Windows Server or Linux.
- Included Features: Web Client and Mobile Client frameworks, OData REST APIs and standard support.
- Pricing: US$1,295 per year.
Enterprise Edition
- Deployment Model: Designed for Linux containerized deployments.
- Scalability: Supports clustered servers, multiple container instances and custom enterprise configurations.
- Pricing: Contact Sales for a customized quote.
Self-hosting gives you control over your infrastructure while still using Lianja’s Web and Mobile deployment framework. It is the right fit when your organization needs to manage its own servers, security policies, network configuration or cloud provider relationship.
b) Lianja Apps Cloud
For organizations seeking a hassle-free, scalable and secure way to deploy Web and Mobile applications without investing in hardware or managing infrastructure, Lianja Apps Cloud provides managed hosting for Lianja applications.
With Lianja Apps Cloud, you can focus on building and deploying your applications while Lianja handles the hosting environment.
Key Benefits of Lianja Apps Cloud
- No Hardware Costs: Avoid purchasing, configuring and maintaining your own servers.
- Maintenance-Free: Reduce the time spent on system administration, updates and infrastructure management.
- Scalability: Choose a plan that matches your user base and grow as your application needs increase.
- Secure Access: Deploy business applications in a managed environment designed for secure Web and Mobile access.
Lianja Apps Cloud Subscription Plans
Lianja Apps Cloud offers subscription plans tailored to different organizational needs.
Developer
US$100 /month
- 20 GB disk space.
- Up to 10 concurrent users.
- Unlimited named users.
- Unlimited apps.
Small Business
US$500 /month
- 250 GB disk space.
- Up to 100 concurrent users.
- Unlimited named users.
- Premium Support.
- Unlimited apps.
Medium Business
US$1,000 /month
- 500 GB disk space.
- Up to 200 concurrent users.
- Unlimited named users.
- Standard Support.
- Unlimited apps.
Large Business
Custom
- Custom Lianja app hosting configuration.
- Unlimited named users.
- Premium Support.
- Unlimited apps.
- Contact Sales for a customized quote.
Each plan is designed for hosted Web and Mobile application deployment. You build applications in Lianja Studio, then deploy them to a hosting option that matches your operational needs.
Conclusion: Flexible Deployment with Lianja
Lianja provides a flexible and cost-effective platform for developing and deploying business applications across Desktop, Web and Mobile.
- Royalty-Free Desktop Deployment - With Lianja Studio, you can develop and distribute Desktop applications without additional desktop runtime licensing fees while your subscription is active.
- Self-Hosting for Web and Mobile - With Lianja Cloud Server, you can deploy Web and Mobile applications on your own servers, private cloud infrastructure or public cloud platforms.
- Managed Cloud Hosting - With Lianja Apps Cloud, you can deploy Web and Mobile applications without maintaining your own hardware or application server infrastructure.
No matter your deployment strategy, Lianja delivers a low-code, high-productivity development platform that adapts to your business needs.
Start Building with Lianja Studio
Build Desktop, Web and Mobile business applications faster, then deploy them with Lianja Cloud Server or Lianja Apps Cloud.
Download Lianja Studio View Pricing
|
Building Secure Business Applications with Lianja
Fine-grained permissions, row-level security and dynamic data masking for Desktop, Web and Mobile apps.
Modern business applications need more than a login screen. Lianja helps developers build secure, data-centric applications with role-based access control, application-level permissions and data protection features built into the platform.
Updated: June 2026
Security Built into the Lianja Platform
In an era where cybersecurity threats are constantly evolving, securing business applications is a top priority for every organization. Lianja provides a practical security model for applications built in Lianja Studio and deployed to Desktop, Web, Mobile, Lianja Cloud Server or Lianja Apps Cloud.
Security in Lianja is designed around authenticated users, assigned roles and controlled access to applications, pages, sections, fields and data. This gives developers and administrators a structured way to protect sensitive information while still keeping applications usable for the people who need them.
Fine-Grained Security: Roles and Permissions
Lianja provides role-based access control so administrators can define users, assign roles and control what each user is allowed to see or do inside an application.
Roles can be applied at multiple levels, making it possible to protect the full application or specific parts of the user interface. This helps teams give users the access they need without exposing functionality or data outside their responsibilities.
Key Role-Based Security Features
- User Roles: Define roles such as Admin, Manager, Sales, HR, Support or Customer, then assign them to individual users.
- App-Level Permissions: Control which users can access an application.
- Page and Section Permissions: Restrict access to specific workflows, screens, sections or operational areas.
- Field-Level Permissions: Protect sensitive fields so only authorized users can view or edit them.
- Action Control: Restrict create, read, update, delete and administration actions based on role.
Why it matters: Role-based security reduces the risk of accidental or unauthorized access while keeping day-to-day workflows efficient for each department, team or customer group.
Row-Level Security: Control Data Visibility
Row-level security helps ensure that users only see records relevant to their identity, role, department, customer account or tenancy. This is especially important for multi-tenant applications, internal systems with departmental boundaries and applications that handle regulated or sensitive data.
With row-level security, developers can apply row filters based on authenticated user roles. For example, a regional sales user can be limited to records for their own territory, while a manager can be given broader visibility.
How Row-Level Security Helps
- User-Specific Access: Show users only the records they are authorized to access.
- Tenant Isolation: Keep each customer, company or business unit limited to its own data.
- Operational Control: Apply different visibility rules for users, managers, administrators and support teams.
- Reduced Exposure: Minimize the amount of data visible to any one user or role.
For businesses building SaaS or shared data applications, row-level security provides an important foundation for protecting customer and organizational data.
Dynamic Data Masking: Protect Sensitive Fields
Dynamic data masking helps prevent unauthorized users from viewing sensitive information while allowing applications to continue working normally. Instead of changing the underlying value, masking controls what the user is allowed to see based on their role.
This is useful when users need access to a record but should not see every field in full detail. For example, a support user might be allowed to verify the last few digits of an account number, while a finance manager can view the complete value.
Benefits of Dynamic Data Masking
- On-the-Fly Redaction: Mask sensitive fields such as account numbers, personal identifiers or confidential business data.
- Role-Based Visibility: Show full values to authorized users and masked values to everyone else.
- Practical Examples: Display values such as
XXXX-XXXX-XXXX-1234 when only partial visibility is appropriate.
- Lower Data Exposure Risk: Reduce unnecessary access to personally identifiable information and other sensitive fields.
Dynamic data masking adds another layer of protection for applications that need to balance usability, compliance and secure data access.
Additional Security Controls for Deployed Apps
Lianja also supports the practical security controls that production applications need when users sign in through Lianja App Center, Lianja Cloud Server or Lianja Apps Cloud.
- Authenticated App Access: Users sign in before accessing published applications.
- Application Tiles by Role: Control which applications are visible to each user.
- User Expiration: Set expiration dates so access can be automatically blocked when a user should no longer sign in.
- Two-Factor Authentication: Support stronger sign-in flows using one-time passcodes where configured.
- Centralized User Management: Manage users, roles, row filters and data masks from the Users Workspace.
Security Planning Checklist
Before deploying a Lianja business application, confirm the following security decisions:
- Each user role has a clear business purpose.
- App, page, section and field permissions match real user responsibilities.
- Row-level security rules have been tested with realistic user accounts.
- Dynamic data masks are applied to sensitive fields that do not need full visibility for every role.
- Administrative accounts are limited to trusted users.
- Deployed Web and Mobile apps have been tested through Lianja App Center or the target hosting environment.
- Access expiration, support procedures and user offboarding are defined before launch.
Conclusion: Secure, Scalable and Practical
Security is a crucial aspect of modern application development, and Lianja helps simplify the implementation of strong access controls through roles and permissions, row-level security and dynamic data masking.
By integrating these security capabilities into applications from the beginning, developers can build secure, scalable and compliant business solutions that protect user data, support operational policies and strengthen customer trust.
|
Overview
In an era where technology evolves rapidly, businesses must adapt to remain competitive. One such company faced the challenge of modernizing its legacy Visual FoxPro-based SoftPay application. The objective was to future-proof the application by migrating it to a modern platform while enhancing its look and feel. By leveraging Lianja’s powerful capabilities, the company successfully transformed SoftPay into a scalable and visually appealing solution.
The Challenge
SoftPay, a mission-critical application developed in Visual FoxPro, had been serving the company reliably for years. However, as support for Visual FoxPro diminished and user expectations for modern interfaces grew, the company faced several key challenges:
-
End of Support for Visual FoxPro: With Microsoft discontinuing support for Visual FoxPro, the application faced potential security and compatibility risks.
-
Outdated UI/UX: The legacy interface no longer met modern user experience standards.
-
Scalability and Performance: The system required a more robust architecture to accommodate growing business needs.
The Solution
The company chose Lianja as the migration platform due to its low-code development environment, cross-platform capabilities, and built-in support for modernizing Visual FoxPro applications. The migration process followed a structured approach:
-
Application Assessment and Planning
-
Analyzed the existing SoftPay codebase to identify core functionalities.
-
Defined modernization goals, ensuring seamless feature parity.
-
UI/UX Revamp
-
Redesigned the user interface with a contemporary, intuitive layout.
-
Leveraged Lianja’s responsive design features for a more engaging experience.
-
Database and Logic Migration
-
Enhancing Functionality
-
Deployment and Optimization
-
Conducted rigorous testing to ensure stability and efficiency.
-
Rolled out the modernized application in phases, minimizing disruptions.
The Outcome
The migration of SoftPay to Lianja delivered significant business benefits:
-
Future-Proofed Technology: The application now runs on a modern, actively supported platform.
-
Improved User Experience: A sleek, intuitive interface enhanced usability and efficiency.
-
Scalability and Performance: The new system supports business growth with enhanced processing capabilities.
Conclusion
By migrating SoftPay from Visual FoxPro to Lianja, the company successfully modernized a legacy application, ensuring continued reliability and competitive advantage. Lianja’s powerful features enabled a smooth transition while significantly enhancing the application's capabilities. This case study highlights how businesses can future-proof their software investments by embracing the Lianja Platform. |
|
Read this article in other languages:
Español | Português | Deutsch
Introduction
Migrating from Visual FoxPro (VFP) is a concern for many businesses, especially those with complex applications that have been built and refined over decades. However, the transition doesn’t have to be overwhelming. Lianja provides a seamless migration path for VFP applications while allowing businesses to modernize and extend their applications using multiple scripting languages. This flexibility ensures that companies can continue developing their applications using readily available developers with expertise in JavaScript, TypeScript and Python.
Lianja’s Multi-Language Support: A Key Advantage
One of Lianja’s most powerful features is its ability to support multiple scripting languages within the same application. Unlike other platforms that force developers to use a single language, Lianja allows you to mix and match languages based on your team's expertise and project needs. This makes it an ideal platform for VFP migrations, as it allows gradual adoption of modern technologies while preserving existing business logic.
Why This Matters for VFP Migrations
- No Immediate Full Rewrite Required: Unlike some platforms that demand a complete rewrite, Lianja allows for an incremental migration. You can start by moving your core VFP application and gradually introduce new technologies.
- Access to a Larger Developer Pool: VFP developers are becoming harder to find, but JavaScript, TypeScript and Python developers are widely available. By introducing these languages, businesses can ensure their applications remain maintainable and future-proof.
- Cost-Effective Development: Companies can leverage existing staff while hiring specialists in modern languages as needed, optimizing costs without disrupting operations.
- Future-Proofing Applications: By blending VFP with modern technologies, businesses can ensure their applications remain competitive, scalable, and adaptable to future needs.
Conclusion
Migrating from Visual FoxPro doesn’t mean abandoning your existing investment. Lianja’s multi-language capabilities empower businesses to transition smoothly while continuously evolving their applications.
With this approach, your application remains future-proof, scalable, and supported by a broad pool of developers—ensuring ongoing innovation without disrupting your business. |
|
|
|
|
|
|
Page 1 of 3 |
