The Next Generation
“The Grand Challenge of Conviva:
Device Dominance”
– Hui, CEO
-
Effort to support device
-
3 weeks on new device dev
-
1 week for each device version upgrade
-
-
More Effort to Maintain than to Expand
-
70% on support vs. 30% on new devices
-
< 10 new devices developed in one quarter
-
-
What will the future be?
Today’s Architecture
Monitor
1. Observe selected APIs
2. Listen to selected events
Proxy
Convert properties and events
to
Conviva Data Model
Insights Client Lib/SDK
Backend
Generic
Computation
Layer
CWS
The New Architecture
Monitor
Monitor purely based on config
Proxy
Insights Client Lib/SDK
Backend
Generic
Computation
Layer
Monitor Configuration Engine
What/How to Monitor
Raw
Info
Client-side Feasibility
| Platform | Library | Notes |
|---|---|---|
| Javascript | Ramda | Will Demo! |
| iOS | Ramda | |
| Android | Reflection, Lambda Expression | |
| Silverlight - C# | Rx |
Impacts and Achievements
- Reduce device-side complexity
- Shorter initial development cycle.
- Simplify integration by removing Conviva data model from client.
- Surprise: it’s a pleasant one, Device Engineers will actually code mostly in the backend!
- Configurable device-side monitoring
- Easy to adjust client behavior when platform upgrades
- Easy to adjust client behavior to add new features
