Sen.se: Mother and the Motion Cookies

Sen.se: Mother and the Motion Cookies

Sensors are showing up everywhere, from wrist wearables like Jawbone UP and Fitbit to the first wave of “smart home” kits. The promise is always the same. Data that helps you understand your day, then nudges you when something matters.

Mother and the Motion Cookies, from connected-objects startup Sen.se, is positioned as a more flexible take on that idea. Instead of buying a single-purpose gadget for each habit, you get one “Mother” hub and a set of small sensor tags. The Motion Cookies. You decide what you want to track, attach a Cookie to the relevant object, and set alerts for the moments you care about.

Definition tightening: A Motion Cookie is a small sensor you can stick to an object. The “Mother” device is the home base that receives the signals and turns them into simple dashboards and notifications.

If you strip away the friendly character design, this is a configurable rules engine for everyday life. The sensors stay the same. The meaning changes based on what you attach them to and what you tell the app to watch for.

Watch the demo video for more.

A sensor kit that behaves like a toolkit

The smart move here is that the hardware is deliberately generic. One sensor type can be repurposed across dozens of “jobs”, depending on where you place it. Toothbrush, medication box, door, bag, water bottle. The product is less about owning the perfect device, and more about reassigning the same device as your priorities change.

In consumer IoT, products only survive if setup friction stays low and the data translates into a simple action.

Why the “Mother” framing makes the tech feel usable

Smart home products often fail at the handoff between capability and comprehension. Mother softens that gap by packaging sensing as caregiving. The real question is whether a sensor system can feel understandable enough that people actually try it. That emotional framing reduces the intimidation factor and makes experimentation feel normal.

Extractable takeaway: When your product is technically broad, give users a friendly mental model and a small first win, then let reconfiguration become the habit that unlocks the long tail of use cases.

What connected-product teams should copy

  • Design for reassignment, not perfection. People’s routines change. Your hardware should survive those changes.
  • Make “setup” the product. If a user cannot get to value in minutes, they will not get to value at all.
  • Translate sensing into verbs. “Brush”, “open”, “arrive”, “drink”, “take”. Verbs beat metrics.
  • Alert sparingly. The fastest way to kill trust is to spam people with “insights” they did not ask for.

A few fast answers before you act

What is Mother and the Motion Cookies?

It is a smart home kit with one central hub and multiple small sensor tags. You attach a sensor to an object, choose what you want to track, and get updates or alerts based on that behaviour.

What is the core idea compared to a single-purpose wearable?

Reconfigurability. The same sensors can be reassigned to different objects and routines, so the system adapts to what you want to measure this week, not what the device designer assumed forever.

What problem is it trying to solve?

Turning ambient behaviour into something actionable, without requiring you to buy a new gadget for every habit or household scenario.

Why does the “Mother” framing matter?

It makes a technically broad sensor system feel more understandable and less intimidating. That framing helps users see the product as practical support, not just instrumentation.

What makes this kind of product hard to sustain?

Reliance on companion apps and backend services, plus the challenge of keeping alerts useful rather than noisy. If the system becomes high-maintenance, it stops feeling like help.

Microsoft: Big Data to Predict Traffic Jams

Microsoft: Big Data to Predict Traffic Jams

Big Data is increasingly being used to find solutions to problems around the world. In this latest example, Microsoft partnered with the Federal University of Minas Gerais, one of Brazil’s largest universities, to undertake research that helps predict traffic jams up to an hour in advance.

With access to traffic data, including historical numbers where available, road cameras, Bing traffic maps, and drivers’ social networks, Microsoft and the research team set out to establish patterns that help foresee traffic jams 15 to 60 minutes before they happen.

What “big data” means in this context

Here, “big data” is not a buzzword. It means combining multiple high-volume signals that each describe traffic from a different angle. Flow and speed data. Camera feeds. Map-layer congestion indicators. And sometimes social or incident signals that explain why conditions change.

How the prediction model is positioned

The mechanism is short-horizon forecasting. Aggregate live and historical traffic conditions. Detect repeating patterns and transitions. Then output a probability that a segment will shift from free-flowing to congested within the next 15 to 60 minutes. The goal is not perfect certainty. It is an early warning that is useful enough to reroute, rebalance signals, or advise drivers.

In urban mobility programs, 15 to 60 minute congestion prediction is a practical layer between raw telemetry and real-world operational decisions.

Why it lands

This works because it targets a time window people actually feel. Short-horizon forecasting matters because it aligns the prediction with the moment when routes, signals, and departures can still change. The real question is whether earlier warning is reliable enough to trigger better decisions before congestion locks in. Useful prediction beats perfect prediction in operational systems.

Extractable takeaway: When a prediction is delivered inside the decision window, it creates value even if it is not perfect. The win is earlier choices, not flawless foresight.

What to steal for traffic prediction

  • Design for actionability: pick a forecast horizon that matches real decisions, not academic elegance.
  • Blend signals carefully: combine steady signals, like flow data, with explanatory signals, like incidents or events, when available.
  • Communicate confidence: a probability and a time window often beats a single definitive “will happen” claim.
  • Validate across cities: portability matters, because traffic behaviors vary by road network and culture.
  • Measure the right outcome: accuracy matters, but reduced delay and better routing outcomes are the real business KPIs.

A few fast answers before you act

What is Microsoft trying to do here?

The project aims to predict traffic jams 15 to 60 minutes ahead by combining traffic flow data, map signals, cameras, and other contextual inputs to spot patterns before congestion forms.

Why is 15 to 60 minutes the useful range?

It is long enough to change routes, adjust signal timing, or delay a departure. It is short enough that conditions have not completely changed since the forecast was generated.

What data sources matter most?

Traffic flow and speed data usually provide the core signal. Cameras, incidents, events, and social signals can add context that improves timing and explains sudden changes.

What does “80% accuracy” actually mean?

It is typically reported as the share of correct predictions under a defined test setup. The real value depends on how accuracy is measured, what baseline is used, and how the prediction is turned into driver or city actions.

Where does this approach fit in a smart-city stack?

It sits between sensing and intervention. Sensors and maps detect current conditions. Prediction estimates near-future conditions. Then routing, signaling, and traveler information systems act on that forecast.