MetaGenesis - The MetaCode CDE

Here is a quick comparison of MetaGenesis and No/Low-Code App Builders

MetaGenesis CDE

Low-Code App Builders

Development Team

Enables non-technical domain experts to participate in defining the application. MetaGenesis is not a no-code platform, but significantly reduces the amount of coding required.
Most of these low-code application builders are intended to replace the technical staff.

Productivity

MetaGenesis is designed to increase programmer productivity and puts them in control of the technology. It makes extensive use of code templates (client and server side), which the programmers can edit to produce an application that meets their requirements. MetaGenesis generates commented source code that is easily understood and managed by the developers.
Replaces most of the technical work with a technology stack chosen by the IDE vendor. The back-end remains a black box.

Interface

MetaGenie does not provide GUI tools, allowing front end developers to continue using their current tools. We leave the UX development to the UX experts and their favorite tools.
Provides a GUI or tools for non-programmers to build the entire application. Most offerings restrict client side development to their own proprietary tools.

Front-End Development

MetaGenie accelerates front end web development by supporting forms and form layouts. Typically a developer creates a sample/template form, using their favorite tool with their desired style and layout. It is then imported into MetaGenie, which separates the "Look/layout" from the form fields. Development proceeds with more forms being defined and the metadata being added (form name, action, method fields, validation...). The forms are rendered to HTML when the application is generated.
Forms are built one at a time with a GUI.

Tech Stack

MetaGenesis currently supports one technology stack (requires Java 11+ compiler, Java Application Server and MySQL or equivalent). MetaGenesis is designed to support many technology stacks in the future.
Most offer one or two technology stacks.

Client Side

The client side is created by the programmer, with some assistance from MetaGenesis for forms. It is supported by the Meta Language MetaL.
Varies by platform, generally not as customizable.

Customization

Easy customization on the server side. All servlet templates are provided as source code and can be easily modified to create new functionality. Once modified they become a new template and MetaGenie generates a new form to manage the template, thus your template becomes part of (your view of) MetaGenesis. (Very meta meta.)
Varies by platform, generally not as customizable.

Deployment

Deploy on a host of your choice.
Host on platforms compatible with the technology stack. Some vendors require hosting on their service.

Summary

A good choice for medium to large and/or self hosted applications. Key advantages:
  • Faster time to market than traditional IDEs.
  • High quality application with complete control over the code.
  • Host almost anywhere.
A good choice for micro-Saas applications with solo entrepreneurs or small non-techical teams. Key advantages:
  • Faster time to market than traditional IDEs.
  • Technical staff not required.

Typical Form Development in MetaGenie

  • The UX Designer-Developer designs and codes an example form with the layout and style they want and import it into the project.
  • The domain expert (or developer) adds a form definition (including field definitions, labels and validators) to the project. With the press of a button the form meta-data is applied to the form template and the form is generated.
  • The developer adds the form to the front end by coding a FORM directive (<mg-FORM:formName;/>) in the html.

The form can be placed on any number of pages. The original template can be updated and/or the form fields can be updated and this will be delivered on the next "application generation".

This site is parked.
MetaGenesis.org an iClick.Media publication
Release A.000.001