WhoBuilt

AI in Practice: From Cloud Privacy Risks to On-Device Solutions

Oct 22, 2025· 8 min· 207 views·Watch on YouTube

Speakers

Matt Pocock, a TypeScript educator turned AI educator, and Szymon Rybczak discuss practical AI use and on-device models with Callstack’s host.

Matt’s move into AI

Pocock says he was initially skeptical after seeing Web3 and other tech trends fade. His business partner encouraged him to explore AI, and he saw potential in tasks like turning unstructured data into structured information. He adds that developers can get started with AI using TypeScript, without first learning Python.

Focus on today’s tools

Asked what advice he has for people who expect AI to do everything, Pocock recommends getting good with the tools available now instead of predicting the future. He says his focus is teaching rather than punditry.

Running models on mobile devices

The host raises the privacy risks of sending private or client data to cloud services. Rybczak describes React Native AI, an open-source library for running models on iOS and Android, with privacy, offline use, and ease of use as motivations. He says it supports custom third-party models and mentions work on Apple’s iOS 26 LLM integration, with Gemini Nano and Gemini Edge planned.

Match the model to the task

Rybczak says simple tasks can use smaller models; rewriting notes as bullet points does not require a top cloud model. Pocock suggests starting with a capable model to establish that a task works, then optimizing for smaller, cheaper, faster models. They discuss automatic model selection as a way to route tasks to an appropriate model.

A smarter code completion workflow

Pocock says he mainly relies on Copilot completion and rarely uses agentic sidebar features. He describes writing code while anticipating the next suggestion and says he would like completion to be smarter or easier to trigger.

Takeaways

  • Start with a strong model to prove a task works, then see whether a smaller one can handle it.
  • Use on-device models when privacy, offline access, or avoiding data transfer matters.
  • Choose model size based on task complexity; simple transformations may not need the largest model.
  • Build with the tools available today instead of relying on predictions about what AI will become.
  • Consider automatic model routing to balance speed, cost, and capability.

Mentioned in this talk

Search inside this talk

What was claimed 6

Related talks

AI in Practice: From Cloud Privacy Risks to On-Device Solutions, Szymon Rybczak, Matt Pocock · WhoBuilt