Objective

The objective of this document is to describe the key concepts that developers need to understand about the mimik Client Library for iOS.

Intended Readers

The intended readers of this document are iOS software developers and system integrators using the mimik Client Library when developing an iOS application.

What You Need to Know Before You Start

In order to get the full benefit of this document, the intended readers should be familiar with the following:

• The basics of the purpose and use of the mimik mim OE Runtime
• The basics of using a mimik Tokens to access and work with the mim OE Runtime

Understanding the Purpose of the mimik Client Library

The purpose of the mimik Client Library is to provide a programmatic way to work with the mim OE Runtime to access information about the mobile device on which the application is running, as well as mobile devices running within a cluster of mobile devices that are hosting the mim OE Runtime. Also, to allow developers to use edge microservices running within a particular cluster.

By leveraging the Core component of the mimik Client Library, developers can build applications compatible with the mim OE Runtime. This not only harnesses the strength of edge computing but also provides an inherent flexibility in its paradigm.

Additionally, this component provides utility APIs that help developers with core operations such as Authentication, mim OE Runtime Setup, deployment of edge microservices and handling of Network calls.

Furthermore, the mimik Client Library Engine component provides additional mim OE Runtime utility APIs, as well as vendoring the actual mim OE Runtime binary into the iOS project.

Understanding the Purpose of the Core and Engine components of the mimik Client Library

The mim OE Runtime is a compiled binary that's intended to run on actual devices.

The reason for having the mimik Client Library split into its Core and Engine components is to give developers the choice of having the mim OE Runtime bundled in within the iOS application or to have it running on a host platform of their own choosing (ie. macOS, Linux, Windows, etc.)

Normally, when the developers intend to run their iOS application on iOS devices, the mimik Client Library Engine can be used to facilitate the integration of the mim OE Runtime binary directly within the iOS application bundle.

However, in order for developers to be able to run their iOS application in an iOS Simulator or through a Mac Catalyst translation layer, it is necessary for the mim OE Runtime to be running on a host platform outside of the iOS application.

Additional reading

In order to get more out of this article, the reader could further familiarize themselves with the following concepts and techniques:

• Creating a Simple iOS Application that Uses an edge microservice.
• Integrating the mimik Client Library into an iOS project.
• Working with mim OE in an iOS project.
• Working with edge microservices in an iOS project.
• Working with AI language models in an iOS project.