Skip to main content

Command Palette

Search for a command to run...

Learning AI as a Mobile Developer — Why I'm Exploring Local LLMs for Mobile Apps

Updated
3 min read
Learning AI as a Mobile Developer — Why I'm Exploring Local LLMs for Mobile Apps
G
I'm a Senior Software developer who loves solving real-world problems and building meaningful products 💡 I currently focus on crafting clean, user-friendly experiences using React Native ⚛️ I enjoy working on challenging projects and constantly learning new things — whether it’s exploring a new framework or diving deeper into existing ones. This space is where I share my journey, the issues I tackle, and the lessons I pick up along the way 🚀

Journey Context

After 6.5 years of building react-native apps. Most of my work has been focused on building production apps, integrating APIs, optimizing performance, and shipping features. But instead of just calling another API, I want to see if we can make the phone think for itself.

But recently, one thing has become very clear.

AI is becoming part of almost every product.

Instead of ignoring it or treating it as a “backend/data science thing”, I decided to understand how AI can actually be used inside mobile apps.

Not from a research perspective. Not from a deep ML theory perspective.

But from a developer perspective.

My goal is simple:

Learn how mobile developers can integrate AI into apps in practical ways.

And that led me to an interesting area:

Local LLMs running directly on mobile devices.

This blog marks the start of my learning journey.

Developer Perspective

In React Native, we usually think about fetch() calls. With Local LLMs, the "backend" is just another local library. Imagine:

An app that summarizes your private notes without ever sending them to a server.

A chat assistant that works in "Airplane Mode."

Zero monthly costs for AI features, no matter how many users you have.

Struggles / Confusions

I’m still a bit confused about Model Sizes. I see models labeled "1B", "3B", or "7B". Apparently, "B" stands for billions of parameters. As a dev used to keeping app bundles under 50MB, the idea of a 2GB "lightweight" model is a bit terrifying. How do we ship that to the App Store without users hating us?

What Surprised Me

I was shocked to find out that modern mobile chips (like Apple’s M-series or the latest Snapdragon) have dedicated "Neural Engines." Our users are literally walking around with AI hardware that most apps aren't even using yet.

Earlier LLMs were massive.

But now we have quantized models that can run in just a few GB of memory.

That means modern phones can actually handle them.

Of course, there are still challenges:

  • model size memory usage

  • battery impact performance on low-end devices

But it's becoming practical.

Closing Thoughts

I’m not approaching this as an AI expert.

I’m approaching this as a mobile developer trying to understand how AI fits into modern apps.

The goal is simple:

Learn AI by building things.

And document everything along the way.

If you're also a mobile developer curious about AI, this journey might help you too.

More experiments coming soon.

AI for Mobile Developers: Learning Local LLMs

Part 1 of 7

AI for Mobile Developers: Learning Local LLMs is a public learning journey documenting how a React Native developer explores practical AI integration for mobile apps. This series focuses on understanding how Large Language Models work and how they can run directly on mobile devices using local inference. Instead of deep AI theory, the goal is to learn from a developer perspective — experimenting with tools, running models locally, and eventually integrating AI features inside mobile applications.

Up next

Tokens and Context Windows: Why My App Can't Remember Everything

Journey Context After deciding to go "Local," I realized I couldn't just throw a 50-page PDF at a mobile LLM and expect it to work. I had to go back to the basics of how these models "read." LLMs are

More from this blog

Govind Maheshwari's blog

12 posts