SDK Entry Points

Richie is the main entry point to the Richie SDK.

Use Richie to construct the top-level SDK objects for ads, books and editions. You can use the shared property if you prefer a singleton, or just pass around an instance. Richie stores the objects you create, so that the first call to makeX creates the X, and subsequent calls return the same object.

If you recreate the Richie instance during the life of your application, call invalidate on the old instance before its deallocated. This will also invalidate all objects created by that factory instance, and their behavior after that is undefined.

RichieAdsController is the main interface for loading ads with Richie SDK.

If possible, you should be using this class instead of RichieAds. RichieAds does not force usage from the main thread but strongly recommends it; this class forces the issue and defines itself to work on the main actor.

If you create a RichieAdsController, yourself, you should call invalidate() on it before relinquishing the last reference. If you use Richie to create it, it keeps a reference to the RichieAdsController it creates and you should use its invalidate method instead.

Main class of Richie’s Editions SDK.

BooksLibraryController is the main entry point for the books functionality of Richie SDK.