Omnis Studio

Omnis Studio is a cross-platform, visual fourth-generation language (4GL) and rapid application development (RAD) environment for building database-driven business applications. Developers write business logic once in the object-oriented Omnis language and deploy it as native desktop software on Windows, macOS and Linux, or — via a JavaScript client — as web and mobile applications. With a lineage reaching back to the early 1980s, Omnis is one of the longest-lived commercial application-development tools still under active development, even though it remains largely unknown outside the community of professional developers who quietly depend on it.

Omnis is unusual among long-lived programming environments in that it has spanned, and survived, nearly every major platform transition of the personal-computing era: from the Apple II and MS-DOS, through classic Mac OS and 16- and 32-bit Windows, to 64-bit macOS, Linux, iOS and Android — carrying its applications forward across more than four decades of hardware and operating-system change.

History & Origins

Omnis began not as a language project but as a British Apple dealership. In 1979, Geoff Smith and Paul Wright founded Blyth Computer Services (later Blyth Software) in the village of Wenhaston, Suffolk — reportedly the first Apple dealer in East Anglia. The company’s first software product, simply called OMNIS, shipped in December 1981: a database application tool for the Apple II, designed by David Seaman and written in Apple Pascal. Writing it in UCSD-derived Pascal proved decisive, because the portability of that environment made it straightforward to move OMNIS onto other machines — a head start in cross-platform support that would define the product for the rest of its life.

Through the 1980s, Blyth turned that head start into a series of firsts. The Omnis 1/2/3 suite (1984) ran across Apple computers and MS-DOS IBM compatibles; Omnis Quartz (1987) was among the earliest GUI database tools for Microsoft Windows; and Omnis 5 (1989) let developers build Windows and Macintosh applications from a single codebase. The Omnis 7 generation (1992–1994) added client/server connectivity to Oracle, Sybase and Informix, and introduced dot notation for object access — a step toward the object-oriented model that the modern product would fully embrace.

That modern product, Omnis Studio, arrived in 1997, the same year the company became Omnis Technology Corporation. Ownership then changed hands several times: a 2000 merger with Pick Systems created Raining Data Corporation, which was renamed TigerLogic Corporation in 2008. In 2016, the Omnis business was bought by OLS Holdings Ltd — a company owned by a group of Omnis developers and distributors — and once again trades as Omnis Software, the arrangement under which it is developed today.

Design Philosophy

Omnis Studio is built around a single, durable promise: write once, deploy everywhere, and keep it running for decades. Several principles follow from it.

• The database application is the unit of work. Omnis is not a general-purpose systems language; it is a tool for building forms-over-data business applications quickly. Screens (called windows and remote forms), data classes, and SQL connectivity are first-class concepts, not libraries bolted on afterward.
• Visual and code, together. Interfaces are assembled in a visual designer, while behavior is written as methods attached to objects and triggered by events. The language and the layout tools are two halves of one environment.
• Cross-platform by default, not by porting. From the UCSD-Pascal OMNIS onward, portability has been a core feature rather than an afterthought, which is why the same application logic can target desktop, web and mobile.
• Backward continuity. Because Omnis customers tend to maintain large, long-lived line-of-business systems, each generation has worked to carry forward existing applications rather than force rewrites.

Key Features

• The Omnis language. An interpreted, dynamically typed 4GL with the traditional constructs — variables, loops, conditionals, methods (procedures) and functions — organized around objects and events. Variables are declared with data-type subtypes such as Character, Number, Date, List and Row (Omnis’s built-in tabular data structures), and Object.
• Visual class library. Applications are composed from classes — window classes, remote-form classes, report classes, object/data classes, and code classes — edited in a visual designer and scripted with attached methods.
• Multi-target deployment. A single application can run as a native desktop client (Windows, macOS, Linux), as a browser application through the JavaScript Client, or as a mobile app via the same JavaScript components wrapped for iOS and Android.
• Database independence. Omnis connects to major SQL databases (Oracle, PostgreSQL, MySQL, SQL Server, Sybase and others) through DAMs (Data Access Modules), and historically shipped its own embedded data file as well.
• Web and integration plumbing. Built-in support for REST, web services, JSON and XML, plus server-side Worker Objects for background tasks, lets Omnis applications act as both clients and services.
• Modern extensibility. Recent releases add a Python interface, Node.js-based JavaScript workers, Git integration, push notifications, and — in the latest versions — AI-assisted developer tooling.

A small flavor of Omnis method code:

# A method that greets the user and stores the result in a variable.
Calculate lvName as "World"
Calculate lvGreeting as con("Hello, ", lvName, "!")
OK message {[lvGreeting]}

Here Calculate assigns a value, con() concatenates strings, and OK message displays a dialog — illustrating the command-oriented, English-like style of the Omnis language.

Evolution

Omnis Studio has evolved by steadily following the platform of the day while preserving the applications already written for it. The late-1990s releases established the cross-platform desktop IDE; version 2.1 (1999) added a web thin client and a Linux build. The 4.x line (2004–2007) layered on Unicode, MySQL and JDBC connectivity, Java and .NET object integration, native Intel-Mac support and web services.

The defining shift of the 2010s was the move to the web and mobile. Omnis Studio 5.2 (2012) introduced a JavaScript-based browser client, and subsequent releases turned those same components into the basis for iOS and Android apps, so that one set of remote-form logic could drive desktop, browser and phone. Version 8.0 (2016) modernized the runtime with a 64-bit, Cocoa-based foundation and HTML/JavaScript components, and version 10 (2019) overhauled the development experience with a redesigned method editor and accessibility improvements.

The current version 11 line (from 2023) continues that trajectory: a refreshed IDE, a Python interface, additional JavaScript controls, and, in 11.2 (July 2025), AI-assisted developer tools — keeping a product first sketched out for the Apple II firmly in the present.

Current Relevance

Omnis Studio occupies a familiar niche: a commercial, professional-developer tool that is invisible to the wider programming public but central to the businesses that build on it. Omnis Software reports that more than 15,000 applications built with the platform are in daily use across healthcare, finance, logistics, manufacturing, real estate, legal, public-sector and other markets — typically the CRM, ERP, stock-control and asset-management systems that run a company’s day-to-day operations.

It is not a language that appears in popularity surveys or trends on social media, and its community is small relative to mainstream stacks. Its appeal is instead longevity and breadth of deployment: organizations that adopted Omnis decades ago can keep evolving the same codebase onto modern desktops, browsers and mobile devices, and a single developer or small team can build and maintain a full multi-platform business application. Development remains active under Omnis Software, with regular releases and a steady stream of new web, mobile and AI-oriented capabilities.

Why It Matters

Omnis Studio is a case study in survival through portability. Born from a small British Apple dealership and a database tool written in Pascal, it became, in turn, one of the first cross-platform database tools, one of the first GUI database tools for Windows, one of the first RAD tools on Linux, and an early mover onto the JavaScript-driven web and mobile clients. Few development environments have remained commercially viable across so many platform eras, and fewer still have done so while letting their customers carry applications forward rather than rewrite them.

Its broader lesson echoes that of other “boring but essential” technologies: a great deal of the world’s everyday business software is built and maintained not in fashionable languages but in long-lived, vendor-supported 4GLs like Omnis — tools optimized less for novelty than for letting small teams deliver and sustain real applications over decades. Omnis Studio matters not because it is widely talked about, but because it is still, quietly, getting work done.