Search Results for "self-contained"

...It includes a set of tools, services, universal runtime and libraries that let you develop, deploy and iterate on Android, iOS, and the web with the same JavaScript/TypeScript codebase. Expo is where client software is developed, and contains the client apps, modules, templates and more; while the Expo development tools are contained in the Expo CLI repository. Try Expo in the browser here: https://snack.expo.io/

Calibre-Web-Automated (CWA) is an all-in-one, self-hosted solution for managing an ebook library that combines the modern, lightweight web UI style of Calibre-Web with the deeper tooling and conversion capabilities associated with Calibre. The goal is to reduce the common “two-service” setup where users run Calibre-Web for browsing and Calibre separately for conversions, metadata fixes, and automation, by packaging those workflows together in a single system.

A conforming WebSocket (RFC 6455) client library for iOS, macOS and tvOS. SocketRocket currently conforms to all core ~300 of Autobahn's fuzzing tests (aside from two UTF-8 ones where it is merely non-strict tests 6.4.2 and 6.4.4). SocketRocket is asynchronous and non-blocking. Most of the work is done on a background thread. You can include SocketRocket as a subproject inside of your application if you'd prefer, although we do not recommend this, as it will increase your indexing time...

Flutter-Notebook is a curated collection of small demo projects for Flutter, designed to help developers learn and practice Flutter UI patterns and behaviors by example. The repository gathers many independent “mini apps” (each focused on one or a few features) so that learners can inspect, run, and understand individual Flutter behaviors in isolation. Demo of common UI behaviors (pull-to-refresh, left-swipe delete, JSON deserialization). Examples of state-preserving page...

...The project is aimed at scenarios where you want a reliable, direct link between a Mac app and an iOS app without relying on Wi-Fi discovery, manual hostnames, or network exposure. A key motivation is that a USB link is inherently constrained to the devices at each end of the cable, which can make the communication model feel more contained and straightforward for certain tooling or companion-app setups. Typical use cases include developer tools, companion displays, device-to-desktop instrumentation, or any workflow where an iOS device acts as a peripheral to a desktop app. The library is intentionally focused: it’s not trying to be a full networking framework, but rather a practical way to “hug it out over USB” for app-to-app messaging.