The Secret Sauce to Our Software Architecture
Our Co-Founder and Chief Product Officer, Filip Eldic, shares a peek into his role and what it takes to build a resilient software architecture.
My job is to innovate. And what I enjoy most is getting to dream. I get to ask “what if?” and imagine perceived realities where technology can function the way I want.
Compromising between imagination and reality
I often find my creativity miles ahead of what’s possible to actually build. Sometimes the impossibility comes from real physical problems – such as Urban Canyoning (that annoying behaviour when your GPS “throws” you onto another street as you enter a built-up urban area). Sometimes it comes from the diversity in mobile devices that behave differently from manufacturer to manufacturer and model to model.
Other times difficulty comes purely from the hardware on the phone such as faulty Wi-Fi or GPS chipsets, but most often issues arise from changes in the Operating Systems of mobile phones, where on occasion, an operating system simply will not comply when our software requests an update on the location of the device.
With average location data technologies, the impact of this unpredictability can be minimal since the use cases do not require extreme reliability. For example, if a native location technology is used to deliver a coupon to customers within 330 feet (100 meters) of a shopping center with a success rate of 60%, this might be an acceptable result for most people.
Pushing the limits of what's possible
Testing and building for resilience
Filip Eldic, Co-founder and Chief Product Officer