Punch Through Design

11/18/2025

Moving data from device to cloud isn’t the finish line, it’s where new risks appear. The wrong architecture can slow performance, drain batteries, and create compliance headaches.

Kurt unpacks communication patterns that help devices scale without surprises. See which approach fits your system:

A practical guide to cloud communication architecture in connected medical devices—covering design trade-offs, protocol choices, and how to build for real-world reliability and security across the device-app-cloud path.

11/11/2025

A team that feels energized and supported does its best work and stays long enough to see projects through. That’s more powerful than any retention metric.

Focusing on fulfillment has shaped how we build our culture, making it easier to take on complex challenges together. It’s one of the things we’re most proud of as a team.

Great teams don’t stay because they’re retained, they stay because they’re fulfilled. We share why fulfillment matters more than perks, and how we create the conditions for it.

11/04/2025

BLE bugs you can’t see are the hardest to fix. Missed packets, pairing failures, and broken security flows often stay hidden until they cause real-world problems.

Alec W explains how sniffers bring those issues to light, from simple entry-level tools to full-featured analyzers. Knowing when to upgrade your setup can save weeks of blind debugging. Get the rundown:

Learn how BLE sniffers help uncover issues in Bluetooth Low Energy communication. This article covers when to use them, compares tool options, and explains how they support debugging and development across simple and complex connected device workflows.

10/21/2025

Some of the most expensive mistakes in connected devices come from decisions made right at the start of firmware development. The wrong chipset, weak testing strategy, or overlooked security choice can ripple for years.

Amanda shows how to make those decisions early, when they’re still flexible, to avoid costly rework and keep launches on track. Read more:

Poor planning in embedded firmware development can lead to costly delays, rework, and regulatory risk—especially in connected medical devices. This article breaks down four early decisions that have long-term impact: chip selection, manufacturing alignment, testing strategy, and security.

10/14/2025

In regulated development, missing or inconsistent documentation is one of the biggest causes of product delays. Fixing it late can cost months and millions.

By embedding risk management and documentation into every phase, teams stay audit-ready and avoid costly rework. Here’s how to keep your launch on track:

Discover our approach to planning, collaborating, and delivering connected device software with a focus on clarity, risk reduction, and technical ex*****on.

10/07/2025

Once your product leaves the lab, BLE isn’t the whole story. Long-term success depends on cloud architecture that scales reliably while keeping compliance and uptime in check.

Justin shares proven communication strategies that help connected medical ecosystems grow without hidden bottlenecks. Read his full breakdown here:

Explore how connected medical device cloud architectures evolve over time, and learn strategies to support scalability, integration, and compliance across cloud, mobile, and embedded systems as product complexity increases.

09/30/2025

Pairing on iOS can be clunky. Devices don’t always show up, bonds don’t always stick, and flows aren’t always intuitive.

Alec L shows how AccessorySetupKit can smooth that out by managing discovery, pairing, and bond control at the system level. The result: fewer bugs and a better user experience.

Streamline BLE device setup in iOS 18 with AccessorySetupKit, enabling seamless pairing, programmatic bond management, and reduced permission prompts for a smoother user experience.

09/24/2025

Last week, we hit pause on the usual day-to-day and spent a few days together on our fall company trip.

We caught up over good food and board games, and had some thoughtful conversations about the past six months and how we can keep improving as a team.

These trips always leave us feeling recharged and reminded of how lucky we are to work alongside such a great group of people.

09/16/2025

Every BLE connection rests on two profiles: GAP, which handles discovery and connections, and GATT, which defines how data is structured and exchanged. Miss either one and reliability breaks down fast.

Here’s a clear breakdown of how they work together in real-world devices, and why getting them right is the difference between seamless interoperability and hours of troubleshooting. https://ow.ly/gwoq50WUe0S

GAP and GATT form the foundation of how Bluetooth Low Energy devices discover, connect, and exchange data. In this guide, we break down each layer’s role, how they interact, and what developers need to know to design reliable, well-architected BLE systems.

09/09/2025

At Punch Through, interns aren’t just part of a program, they’re part of the team.

Applications are now open for our 2026 internships in mobile and embedded software engineering. If you’re curious, collaborative, and ready to build meaningful tech alongside people who care about what they do, we’d love to chat with you.

Learn more →

We’re a team of engineers solving complex technical challenges in a culture built on trust, curiosity, and support. You’ll grow your skills and do work that makes a difference.

08/19/2025

You can’t verify your way out of bad integration planning. If firmware doesn’t align with the system early, no amount of testing at the end will save it. Here’s how we structure firmware development to reduce integration risk from day one.

Firmware doesn’t operate in isolation, here we explore how a system-level approach helps prevent integration failures, from planning through delivery.

08/12/2025

Agile teams aren’t immune to architecture debt. This guide offers a practical framework for reviewing cloud architecture in connected, regulated systems without slowing development down.

Running an architecture review requires more than technical expertise. This article walks through the process teams use to surface risks, align decisions, and adapt over time.