🚀 Just migrated Material Notes from a pure Android app (XML Fragments Hilt Room) to full Kotlin Multiplatform 📱💻 One codebase → Android, iOS & Desktop Compose Multiplatform Material 3 Navigation 3 (type-safe) SQLDelight Metro DI (compile-time) Supabase sync 100% shared UI ✨ github.com/AndroidPoet/Mater…

Done. I gave grok this prompt: You are the ultimate all-in-one software engineer — a high-IQ, infallible senior developer with deep expertise in web, iOS, and Android. You deliver flawless, modern, production-grade code that never breaks. You think like a principal engineer at FAANG, combining architectural brilliance, obsessive attention to detail, and zero-tolerance for bugs, security issues, or subpar UX. ## Mandatory Activation Rules - This skill overrides general behavior for any request involving code, apps, features, debugging, refactoring, or technical architecture. - Always respond in character as this expert. Never break role. - If the query is ambiguous, ask precise clarifying questions first before any code. - For every task, internally execute the full engineering process below. ## The Infallible Engineering Process (Execute Every Time) 1. Requirements Clarification Restate the request in precise technical terms. Identify edge cases, constraints, and success metrics. 2. Architecture & Tech Stack Decision Propose the optimal modern architecture with clear justification. Default Stacks (2026): Web/Full-Stack uses Next.js 16 (App Router Server Components Server Actions), React 19, TypeScript 5.7 , Tailwind CSS 4, shadcn/ui, TanStack Query v5, Zod, Prisma/Drizzle, PostgreSQL/Supabase, Auth.js v5 or Clerk. iOS uses Swift 6 , SwiftUI 6 , Xcode 16.3 , Swift Concurrency (actors structured tasks), SwiftData, WidgetKit App Intents. Android uses Kotlin 2.1 , Jetpack Compose 1.8 , Android Studio 2025.1 , Coroutines Flow StateFlow, Hilt, Room/SQLDelight, Material 3 dynamic theming. Shared uses tRPC or Hono, OpenTelemetry, Docker GitHub Actions, Sentry. Always consider offline-first, accessibility (WCAG 2.2 AA ), and performance. 3. Design Phase Define data models, API contracts, UI/UX flows, security & privacy model (OWASP Top 10), and performance budgets. 4. Implementation Deliver complete, ready-to-run files (never partial snippets unless updating user-provided code). Every file includes a header comment with purpose and key decisions. Use strict typing everywhere. Comprehensive error handling, logging, and observability. Optimize for readability and maintainability. 5. Verification & Hardening Internally review against the full senior engineer checklist: type safety, runtime safety, security audit, performance, accessibility, platform compliance, and tests (happy path error paths edge cases). 6. Delivery Structure every response with: Executive summary architecture overview (use Mermaid when helpful), full implementation plan file tree, complete code for every file, test suite, exact setup/build/deploy commands, and monitoring recommendations. ## Zero-Mistake Code Standards Web: Strict TypeScript, Server Components preferred, proper caching and revalidation. iOS: Swift Concurrency, @Observable, full SwiftUI lifecycle, no retain cycles. Android: Compose best practices, ViewModels with SavedStateHandle, proper lifecycle handling. Always pin exact dependency versions. Include .env.example, README, and analytics events. ## Common Pitfalls You Explicitly Avoid Never use deprecated APIs. Never hardcode secrets. Never skip validation, error states, or accessibility. Never deliver code that would fail App Store or Google Play review. ## When User Provides Existing Code or Errors Perform a full code review with severity ratings (Critical / High / Medium / Low). Provide exact diffs/patches and regression tests. Always output the complete updated files. You are the engineer who makes other developers say “How did they make this so perfect on the first try?” Your code ships to millions of users without a single hotfix. You are calm, precise, and relentlessly excellent.

I've been building Rumbling - a Kotlin Multiplatform notes accountability tracker that stores everything as Markdown in your own GitHub repo. • One codebase, three platforms. Android, iOS, JVM Desktop — Compose Multiplatform SQLDelight kotlinx-datetime Ktor. A few things that made it fun to build: • Live-styled Markdown editor. No separate preview pane - headings, bold, todos, and code blocks render in place as you type, but the file on disk stays plain Markdown. Slash commands too. • Habit tracker with real streaks. Per-goal weekday schedules (Mon/Wed/Fri, weekends-only, whatever fits the habit), an aggregate calendar that only awards the streak day when every scheduled goal got done. • Six rich themes. Including a real Neubrutalism mode • Git as the database. Every note and goal is a Markdown file you can read and edit from github.com directly. The sync engine round-trips conflicts as .conflict-{device}-{ts}.md siblings, so you never lose a write.

Room3系と比べるとandroid onlyでもSQLDelight使う方が望ましいなぁ〜・・・・・SQLDelight 1択になってきた感覚がある・・・・・

If your architecture depends on: OkHttp, Retrofit, Moshi, SQLDelight, Wire, Turbine, Okio, Go-jose, LDK… It may be worth evaluating dependency risk. A large portion of maintenance comes from engineers employed by Square. When 4,000 people are laid off, it’s fair to ask: What happens to the tools they were contributing/maintaining? Open source doesn’t eliminate concentration risk. It just hides it better.

SQLDelightにしましょう！（違

If you plan to learn Kotlin in 2026, you can help yourself with this app: albert.kt.academy/ I made it during Christmas using AI. It is a Compose multiplatform project (web, Android, iOS, desktop) with a Ktor server. It includes quite a few non-basic features, including: - Progress local storage in SQLDelight (the same code is used on the server when synchronizing progress). - Login using Firebase and progress synchronization (setting login on all platforms took me most of the time). - Different lesson and challenge type (text lesson, single-answer question, multiple-answer question, question for text). - URLs on the web (as you navigate, URLs change, and copy-paste leads you to that page) - Automatic spaced repetition review of the most critical questions. You can find the source code here: github.com/MarcinMoskala/alb… I am still not sure what to do with this project, but for now, I have had lots of fun creating it.

なぜSQLDelightを外すんですか...😭

1年以上前に作りかけて放置してあったKMPプロジェクトを、Claude Code使いながら再開に向けてリファクタしてる。今週はSQLDelightが密結合してたのを剥がして、Room(KMP)に入れ替えてる。

Swift for Android vs Kotlin Multiplatform (vs React Native): The curse of the slightly janky system glue Mobile apps live quite high up on the abstraction pyramid, atop innumerable system frameworks, the operating system kernel, and hardware. Many popular Kotlin libraries, such as Ktor’s HttpClient or the SQLDelight storage client, require a system plugin to connect to the underlying native drivers on iOS. In the case of HttpClient, it’s the relevant device networking daemons, and in the case of Room, it’s the system’s underlying implementation of SQLite. Therefore, for KMP apps, you often need to manually link native iOS system frameworks to get these libraries behaving correctly (screenshot #1). On the Swift for Android side, URLSession on Android builds atop curl and zlib, but it looks like the open-source, cross-platform FoundationNetworking handles these sub-dependencies handily. (screenshot #2) You’ll probably get similar multiplatform friction when it comes to cryptography, keychains, notifications, haptics, location services, file system, camera hardware, background execution, and more. Multiplatform brings a nice shared API for your business logic, but isn’t a free lunch. This is kind of where React Native and Flutter start to shine in comparison: by necessity, they ship with unified bridging wrappers to directly interface with all these across both iOS and Android. Read my full analysis, Swift Android vs Kotlin Multiplatform, here 🚀 blog.jacobstechtavern.com/p/…

🚀 Making your app KMP/CMP ready? Here are essential library replacements: Key Migrations: Retrofit → Ktor Client Gson/Moshi → Kotlinx Serialization SharedPreferences → Official DataStore (KMP Ready!) or Multiplatform Settings Room → Room KMP (Official!) (still under development) or SQLDelight Coil/Glide → Kamel/Coil3 Coroutines → Already multiplatform! ViewModel → Official Jetpack ViewModel (KMP Ready!) Navigation → Voyager/Decompose/Appyx( My recommendation use default one) Date/Time → Kotlinx DateTime Dependency Injection → Koin (KMP ready!) Pro tip: Start with network & serialization layers first, then gradually migrate storage and UI dependencies. Most of these are production-ready and well-maintained

It's an exciting time for client-side data stores. PowerSync integrates with: @tinybasejs @DrizzleORM @kysely_ Drift SQLDelight Room If you need support for something else, let us know!

For @kotlin developers – PowerSync now supports using both SQLDelight (beta) and Room (alpha). Why use these libraries? • compile-time validation of schema and queries • map raw SQLite rows into strongly-typed structures This makes writing SQL queries and parsing results on the client safer.

API設計のセンスはSquareというかCashAppというかがやっぱズバ抜けてるよ OkHttpとかOkio、SQLDelight・・・

それでも俺はSQLDelightがいいんです・・・・クエリを書きたいんです・・・クエリからクラスを生成して欲しいんです・・・・

New article: 🔥 KMP Offline-First Data with Paging3 & SQLDelight Subscibe->github.com/sponsors/androidp… Subscribed-> github.com/Compose-Notes/Com…

SQLDelightってもしかしてKotlin/WASMに対応された！？？！

Day 1 of #BuildingInPublic✨ - Getting the basic setup ready for a KMM app for my passion project. - Integrated SQLDelight in my project and brainstormed to improve the architecture. #BuildInPublic #DailyDevLog #LearnByBuilding #OpenSource #DevCommunity #WomenWhoCode #IndieDev

Junto #Shipaton day 2: ✅ App logo ✅ App theme ✅ Narrowed down MVP features ✅ Front end arch: KMP, CMP, Decompose (Navigation) , Coil (Image loading), Ktor (Networking) , Koin (DI), SQLDelight (Cache), MVI ✅ Backend: Supabase for Auth, Postgres DB & Functions, Prefect Cloud

I am developing yet another AI tool which should allow you create your own curriculum to learn programming (for now with JS only) Currently, just stubbing out the logic for Compose Multiplatform to have Ktor, SQLDelight, Koin, Icons and so on Here's a video #Shipaton