Skip to end of metadata
Go to start of metadata

To properly design and develop cross-platform mobile apps with Crosslight, it’s important to understand the anatomy of a Crosslight application. In this section, you will learn what a Crosslight application looks like and what it comprised of.

A Crosslight application typically consisted of a portable assembly where all sharable application code reside, and each assembly for each platform that the application is targeting.

The following diagram illustrates the anatomy of Crosslight applications.

As the diagram implies, the core assembly is the foundation of the Crosslight application which contains all sharable application code – including data access layer, business process layer, domain objects, user interaction and application logic layer – which will be consumed by each of the targeted platform.

Since most application code are shared and unified in a single core assembly, the platform-end typically contains only a small portion of platform-specific layers that aren’t ideal to be shared. This includes thin controller layers that wrap the platform-specific controllers, and metadata files that describes the user interface and layout definition.

With the Crosslight application anatomy designed this way, it maximizes code sharing to a whole new level with elegant architecture that promotes greater efficiency in building maintainable and extensible cross-platform mobile apps.