Webinar Summary
The following summary is auto-generated from the webinar recording.
Prototypes are often the fastest part of an IoT journey. The harder work begins when a team has to make the product reliable, supportable, manufacturable, secure, and useful in real homes or businesses.
That was the focus of a recent Blues webinar with Hello Everyday, an age-tech company building connected devices that help older adults age in place with autonomy, dignity, and safety. Their products use presence sensing, temperature monitoring, cellular connectivity, and SMS-based notifications to connect an older adult with trusted family members, neighbors, or caregivers.
For connected-product teams, the Hello Everyday story is useful because it is not just about sensors or firmware. It is about the practical decisions that determine whether a connected product can move beyond a lab bench and into real-world deployment.
Designing for the User, Not the Technology
Hello Everyday started with a clear constraint: many older adults do not want or cannot reliably use complex technology. Touchscreens can be hard to operate. Apps introduce friction. WiFi setup can fail. Passwords are often forgotten. Even small controls can become difficult when dexterity or vision changes.
So the team designed the core device around a simple idea: plug it in and it works.
The user-facing interface is intentionally minimal. The device uses a light to communicate basic status: green when things are working, red when something needs attention. There are no cameras, microphones, passwords, or wearable requirements. That was not an afterthought; it was central to the product's acceptance.
The simplicity also reflects a privacy decision. Hello Everyday is not trying to create a surveillance device. It is trying to provide reassurance and timely alerts while preserving dignity. In practice, that meant choosing presence sensing and text-based communication over cameras, voice assistants, or app-heavy workflows.
For teams building connected products, this is a useful reminder: simple for the end user often means more complexity behind the scenes. The product may look quiet and minimal on the outside, but the backend, support process, diagnostics, and deployment model have to carry more of the load.
Why Hello Everyday Chose Cellular Over WiFi
One of the clearest technical lessons from the webinar was the team's decision to move away from WiFi.
Early on, Hello Everyday considered using WiFi and an app. But field experience quickly exposed the fragility of that approach. A customer could change a modem, an assisted living facility might have unreliable WiFi, or a family member might not understand that a network change would take the device offline.
For a safety-oriented product, that was not acceptable.
Instead, the team standardized on cellular connectivity using Blues Notecard. The Blues Notecard gave the team a way to build self-contained devices that did not depend on a home router, facility IT department, or user-managed network credentials.
Cellular was not magic. Coverage still varies by location, building construction, and placement. But by removing WiFi onboarding and maintenance, Hello Everyday reduced a major source of deployment friction.
The team also made practical RF design choices:
- They used a recommended antenna.
- They kept the PCB ground plane clear near the antenna to avoid detuning.
- They oriented the antenna vertically for better omnidirectional performance.
- They learned that placing a device on a countertop could improve connectivity compared with plugging directly into a wall outlet near wiring.
Those decisions matter because cellular performance is not just a modem decision. It is also an enclosure, antenna, board-layout, and installation decision.
Building Around Intermittent Connectivity
Even with cellular, real-world connectivity is imperfect. Hello Everyday had to account for delayed transmissions and intermittent coverage.
The Notecard can cache data when it cannot immediately connect and send it later. That behavior is useful, but it also changed how the team interpreted device reports. If six reports arrive at once after a period of poor connectivity, the backend needs to understand that they were delayed rather than assume everything happened at the moment of receipt.
Hello Everyday addressed this by timestamping data when routed through Notehub and building server-side logic to detect cellular delays. The team also created reporting to identify devices that appear healthy at a high level but show delayed communications underneath.
That distinction is important. A dashboard that only shows "last received data" can mask connectivity problems. A production system needs to understand when the data was generated, when it was transmitted, and when it was processed.
For teams implementing similar workflows, the Notehub documentation is a good starting point for understanding routing, device events, and fleet workflows.
Presence Sensing Without Cameras
Hello Everyday's primary device uses millimeter-wave radar rather than passive infrared sensing. The radar operates at 24 GHz and is sensitive enough to detect small movements, including breathing. That lets the device detect human presence even when someone is sitting still.
Radar also gives the system useful data beyond simple motion:
- Distance to the detected target
- Strength of the radar return
- Persistent patterns over time
That data helps the team handle real home environments. Pets, balloons, ceiling fans, and room layout can all affect sensing. For example, the team described using distance gating to ignore objects close to the sensor, such as a cat climbing on a counter. They can also use return strength to distinguish smaller pets from people in many cases.
Ceiling fans and balloons introduced other lessons. A fan may produce a consistent echo at the same distance over long periods. A Mylar balloon may move enough to look like activity. These edge cases are not unusual failures; they are exactly what happens when a product leaves the lab.
The broader takeaway is that connected products deployed into homes must be tunable and observable. You may not be able to control the environment, so the system needs enough diagnostic visibility to explain what it is sensing.
Temperature Measurement Is Harder Than It Looks
The Hello Everyday device also includes temperature monitoring to help identify unsafe indoor conditions, such as a home that becomes too hot or too cold.
At first glance, temperature seems straightforward. Many components include temperature sensors. But internal chip temperature is not the same as room temperature, especially inside a powered enclosure with a cellular modem and microcontroller generating heat.
The team iterated on the PCB and enclosure design to improve measurement accuracy. They moved the temperature sensor toward a corner of the board, reduced heat conduction through copper, interrupted part of the ground plane, and positioned the sensor near a screw connected to the case so the enclosure could act more like an external thermal reference.
For calibration, they used a practical low-cost approach: a reptile incubator with heating and cooling, validated against a better temperature sensor. It was not a lab-grade environmental chamber, but it was good enough to characterize offsets and improve real-world performance.
This is a good example of engineering judgment. Production development does not always require expensive equipment, but it does require careful thinking about what is actually being measured.
Key Technical Takeaways
Several technical themes stood out from the webinar.
First, connectivity choices shape the whole product experience. WiFi may reduce hardware cost in some designs, but it can increase support complexity and deployment risk. Cellular can simplify installation, especially when the end user cannot be expected to manage networking.
Second, store-and-forward behavior must be reflected in backend logic. Cached messages are valuable, but applications need to distinguish delayed data from real-time data. Teams using Notecard should become familiar with the Notecard API reference and design their event processing accordingly.
Third, diagnostics are not optional. Hello Everyday monitors missing hourly reports, reviews early deployments closely, and uses sensor-level diagnostic data to understand false triggers or poor placement.
Finally, environmental sensing requires physical design work. Antenna placement, enclosure geometry, heat transfer, and mounting location can all affect product reliability.
Product and Design Lessons
Hello Everyday's product decisions were shaped by direct engagement with older adults and caregivers. The team did not build first and ask later. They involved prospective users early, learned what felt invasive, and designed around existing relationships.
That led to several important product choices:
- Text messages instead of mandatory apps
- Secure short-lived links for richer dashboards
- No cameras or microphones
- Optional notification modes for different privacy preferences
- Support workflows that do not assume technical skill from the user
The team also learned that customer acquisition and channel strategy are part of product-market fit. Direct-to-consumer sales through broad online channels were not automatically effective because the product created a new category and often needed an intermediary, such as a professional, community, or trusted organization, to explain its value.
For connected-product teams, the lesson is clear: technical validation is not the same as market validation.
Notable Implementation and Architecture Decisions
Hello Everyday kept its team and operations intentionally lean. That influenced several architecture and manufacturing decisions.
The devices use off-the-shelf modules where possible, including pre-certified radio components. That helped reduce the burden of intentional radiator certification, though the final product still required testing for unintentional emissions. The team also had to address an unexpected issue from a USB power supply that introduced noise, despite carrying its own markings.
For enclosures, Hello Everyday continues to use 3D printing. That gives the team flexibility to iterate quickly, build on demand, and avoid committing too early to injection molding. At their current scale, the tradeoff is acceptable. The next question will be when volume justifies tooling.
This is a common production inflection point. Early tooling can lock in design mistakes. Too much manual production can constrain growth. The right answer depends on volume, working capital, design stability, and support burden.
For teams still moving from prototype hardware to deployable systems, the Blues Developer Portal and Blues kits can help accelerate early development while leaving room for production-oriented design decisions later.
Moving Beyond the Prototype
Hello Everyday's journey reinforces a practical truth: a connected product succeeds when the technical architecture, user experience, support model, and business model fit together.
The team's choices—cellular over WiFi, text over apps, radar over cameras, 3D printing over early tooling—were not isolated engineering decisions. They were product decisions grounded in the needs of older adults, families, and care communities.
If you are building a connected product, especially one that has to work in uncontrolled environments, the lesson is to test early, listen closely, and design for the messy realities of deployment.
Watch the webinar recording to hear the full conversation with Hello Everyday, or learn more about how Blues helps teams build connected products beyond the prototype.
