IoT device-management apps: ownership, fresh data, and command outcomes
Plan identity, BLE/MQTT responsibilities, timestamps, alarms, and verifiable command results, with an explicit boundary for hardware integration.
Read article
AppKernia architecture through one article bookmark
Trace the browser, same-origin BFF, App API, and PostgreSQL to understand session recovery, application scope, duplicate writes, and shared contracts.
Read article
Shared accounts in Next.js and uni-app x: sessions, refresh, and boundaries
Understand the BFF, HttpOnly cookies, and mobile secure storage, then test reloads, concurrent refresh, revocation, and application scope.
Read article
Adding AI Customer Support with a Loader Script
A support widget with controlled product information, server-side secrets, staff handoff and signed user identity.
Watch video
Understanding uni-app x Performance: Compilation, Rendering and Bridging
Separate compilation, rendering and native bridging, and distinguish platform benchmarks from measurements in your own project.
Watch video
A Push API Says Success. Did the User Actually Receive It?
After integrating APNs, FCM, HarmonyOS and six Android vendor channels directly, we distinguish four push stages and seven send outcomes. Here is how those distinctions determine retries, permissions and release acceptance.
Read article
One Account Across Web and App: Why You Must Keep Tokens Separate
Two clients can share a user's profile while keeping their sessions separate. Using AppKernia's implementation, this article explains token storage, identity recovery after a reload, concurrent refreshes across browser tabs, and replaying writes.
Read article