Realm is a mobile database that uses native objects mapped to a custom database engine rather than SQLite. It allows for complex data modeling with linked objects and advanced queries. Realm prioritizes ease of use, performance, cross-platform support, advanced features like reactive patterns, and community/support. Major companies like Twitter and Starbucks use Realm for their mobile apps.
DBACCESS RESEARCH
The document discusses DBAccess, an iOS ORM (object-relational mapper) that provides an alternative to CoreData. It highlights features like automatic modeling from class structures, a fluent query interface, an event model for tracking database changes, and support for managed and unmanaged objects. The document also provides code examples for setting up a project with DBAccess, creating data objects and properties, performing queries and handling results, and using the event model.
This document discusses how to use a third party Objective-C library in a Xamarin.iOS app. It involves:
1. Creating an Objective-C static library project in Xcode and importing the third party files.
2. Using Objective Sharpie to generate C# bindings from the Objective-C headers.
3. Creating a Xamarin.iOS binding project and linking the static library.
4. Creating a Xamarin.iOS app project that references the binding project to use the third party library.
The document discusses how to use a custom Objective-C class library in a Xamarin.iOS application. It involves:
1. Creating a static library project in Xcode containing the Objective-C classes.
2. Using Objective Sharpie to generate C# bindings.
3. Creating an iOS binding project in Xamarin.
4. Referencing the binding project from a Xamarin.iOS app to use the Objective-C classes.
A Watch app for watchOS 2 consists of two separate bundles that work together to deliver your content to the user. The Watch app itself contains the storyboards and resource files needed to display your interface, and the WatchKit extension contains the code and resources needed to update that interface.
In watchOS 2, the extension runs on the user’s Apple Watch instead of on the user’s iPhone, as was the case in watchOS 1. Moving the extension to Apple Watch makes communication between the Watch app and extension much faster and makes it possible for your app to run when the user’s iPhone is not present.
The document provides Apple Watch design specifications and guidelines. It discusses display sizes, layout, typography, color, customization, home screen icons, menu icons, animations, and includes references. Key recommendations include using one image resource for both display sizes, avoiding too much information on one screen, limiting side-by-side controls, aligning elements to the left, choosing appropriate system fonts and colors, and embracing simplicity in icons.
This document provides guidelines for designing user interface elements for the Apple Watch, including labels, images, groups, tables, buttons, switches, sliders, maps, date labels, timer labels, and menus. Key recommendations include sizing images and elements appropriately for the 38mm and 42mm watch displays, using groups to arrange content horizontally and vertically, limiting tables to about 20 rows, creating full-width buttons, and including labels and icons to clarify menu actions.
The document provides guidelines for designing interfaces and interactions for Apple Watch apps. It covers designing for the small screen, including using hierarchical or page-based interfaces, gestures like swipes and taps, and elements like labels, images, groups, tables, buttons and menus. It also provides tips for colors, typography, animations and icons to create polished Apple Watch apps within these constraints.
QuickBlox is a cloud communication backend that allows developers to add features like instant messaging, video/voice calling, and push notifications to their mobile apps. It includes modules for chat, video calling, voice calling, push notifications, user management, content storage, custom objects, and more. Developers can use QuickBlox to build communities around their apps and enhance user engagement through real-time communication features.
This document discusses using Touch ID authentication on iOS devices running iOS 8 or later. It provides an overview of the LocalAuthentication framework for evaluating Touch ID policies, links to Apple sample code for integrating Touch ID with keychain access, and lists some open source projects and references for working with the Touch ID API.
The document discusses iOS Keychain, which is an encrypted container for securely storing private information like passwords and certificates on iOS devices. Keychain stores data for each app separately, but data can be shared between apps with the same access group. The document provides code examples for adding, finding, updating, and removing items from the Keychain via API methods like SecItemAdd, SecItemCopyMatching, and SecItemDelete.