ersinkoc/phonebox

Source
GitHub
First trending
Category
Design and UI
GitHub stars
3,246
Main language
C#
Website
ersinkoc.github.io/phonebox (opens in a new tab)

This page introduces an external open-source repository. It is not an HDATF product.

ersinkoc/phonebox

What it does

PhoneBox turns an Android phone into a configurable desk display and touch controller for a computer. An Android application pairs with a desktop agent on Windows, Linux or macOS and shows information through configurable widgets and pages. Inputs include system measurements, supported coding-agent sessions, service data, webhooks and touch actions, while outputs include live panels, notifications and configured computer controls. A browser editor arranges layouts, and widgets cover system resources, coding quotas, media, calendars and automation. The Android WebView sends agent requests through a native proxy, using an adb tunnel over USB or paired HTTPS with a pinned certificate over Wi-Fi. Live events use a server-sent-events stream with polling as a fallback, and sensitive commands and integration credentials remain on the computer according to the documentation. The core panel needs no PhoneBox cloud account, but optional weather, quota, GitHub and other integrations contact external services. It requires Android 7 or later, and widget availability depends on host hardware, tools and permissions, so the documented platform support is not identical for every control.

License

MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.

More in this category

  • sveltejs/svelte
    Svelte is a component compiler and user-interface framework for developers building interactive web applications. Its inputs are component source files combining markup, styles and JavaScript or supported TypeScript syntax, with application data and user events supplied at runtime. Compilation produces JavaScript component modules and associated styling for interfaces that update the browser document when relevant state changes. The compiler entry point parses source, validates options, analyzes components and transforms the result, so it is more than a collection of visual widgets. Its reactive runtime tracks dependencies and schedules affected reactions, while state objects and arrays can use proxies to trigger updates for changed properties. Official examples connect state to event handlers and demonstrate snapshots for libraries that do not accept proxies, but destructuring and sharing reassigned state across modules have documented limitations. Development commonly uses Node.js and Vite, and the official guide recommends the separate SvelteKit application framework or a direct Vite integration with routing selected separately. Core Svelte does not require an AI model or hosted service, and its interface capabilities do not themselves provide enterprise authentication, data connectors or durable workflow execution.
  • deepseek-ai/chat-demo
    chat-demo is a static DeepSeek chat interface for users and developers who want an API client without an application backend. Users provide an API key, prompts, attachments, or voice input and receive streaming replies with supported reasoning, search citations, and rendered Markdown, mathematics, or diagrams. The browser calls the configured API directly, using Anthropic-compatible Messages and Files interfaces and separate speech endpoints. Conversation branches support prompt editing, regeneration, and switching between alternative replies. API keys and settings stay in localStorage, while conversations and original attachments are stored in IndexedDB, but submitted content is sent to the API service. A release archive can be opened through its index.html, while source development uses Node.js 22.12 or newer, pnpm, React, TypeScript, and Rspack. The default origin is api.deepseek.com and the documented default model is deepseek-flash, so another service must support the same extensions and cross-origin requests. ZIP history import replaces local history after validation, exports omit original non-image attachments, and deleting local chats does not remove files already uploaded to the service.
  • vercel-labs/ui
    UI SDK is a UI library for developers and coding agents to reuse interaction behaviors. It is not a finished business app or model, but a toolkit for keyboard navigation, focus, selection, popups and accessibility attributes. Developers define state, actions and component parts, then render actual elements through a framework adapter. It supplies a shared core and adapters for React, Vue, Svelte, Solid and Web Components. The official example connects a search input and clear button to one behavior definition. The dialog source also separates state, slots and actions exposed to agents. Getting started requires connecting core and the appropriate framework package to an app; the agent skill is a separate addition. Installing packages does not automatically convert existing screens. The product is beta, so APIs and behavior may change and accessibility still needs testing in the actual interface.
  • expo/exact
    Exact is an application runtime for developers who want one interface definition to serve web, macOS, iOS and Linux apps. Its inputs are Contract, a declarative language for views, state and actions, plus TypeScript or Rust data logic. The compiler produces a plan that becomes browser DOM and CSS on the web, while a Rust runner and layout kernel drive native controls or painting on other hosts. Data reads and writes cross a typed boundary, and declared grants restrict access to networking, files, SQLite and secrets. An agent driver exposes tree inspection, screenshots, interaction, state and clock control through a shared interface, with Contract tests reusable across hosts. The repository includes todo and local notebook examples rather than an already configured business application. Setup depends on a source checkout, Rust, pinned Bun and Chrome, with Xcode required for Apple targets and a pinned Hermes JavaScript runtime for native TypeScript. This is a changing pre-1.0 project without compatibility guarantees, while Windows control parity and delivery, Android packaging and Linux editing remain incomplete.
  • anomalyco/rune
    Rune is a UI framework that builds interfaces from Rust code and renders them on the GPU. Its main documentation targets macOS, Windows, Linux and the web and covers interface inspection by coding agents as well as people. Inputs are application state, view functions and human or scripted interactions; outputs are running interfaces or headless PNGs and element trees. The inspected hello example changes state when a switch is clicked and updates its text and knob position accordingly. Its test uses virtual pointer input and frame advancement to check the state change and knob movement. Core documentation describes layout, text, theme tokens, spring animation and headless input. Adoption requires connecting Rune as a Rust project dependency and writing state and views; installation does not convert an existing application. It is pre-release, so the documentation recommends pinning a specific dev revision, and target-platform graphics, real input and accessibility support require separate validation before adoption.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.

View on GitHub (opens in a new tab)