Skip to content

Conscious innovation

Opinion Articles

António Abreu

Bliss Applications

When I finished college, my first application was to Linden Labs. This San Francisco company created the virtual community Second Life, a world for residents to create the digital life they wanted. At the time, even though I was familiar with the world of e-sports, I believed there was a future there—spaces where reality blends with the digital and where the limitations of earthly life become dependent only on our imagination. 

Today, we are one step closer to this future. Combining mixed reality, Gen AI, and brain-computer interfaces will bring the concept and potential of Second Life into something that blends, intertwines, and confuses with our first life. Today, taking this step is no longer appealing to me. I’m still fascinated by new technologies—I’m eager to experiment, and what’s coming excites me more than it scares me—but, thinking about the time we spend numb in front of a screen, it’s certain that many of the applications of these innovations won’t be beneficial. I am convinced that it is our duty as parents and professionals to ensure that these innovations work to bring us closer to what matters most and not the other way around, or at least that they give us back time to use freely with our people and with the real world around us. 

 

We know that big tech will dictate how humanity’s attention is applied. Unfortunately, much of it will be wasted, reinforcing a thirst for more information consumption and an intolerance for life in real-time. Knowing that this is the way forward, we can cultivate a common awareness of the impacts of this inattention and try to create a balanced relationship between the analog and the digital. We know that these technologies will be used by companies in our corner of Europe, particularly in digital products and experiences that will impact the daily lives of the Portuguese people. 

 

To promote this transformation, we need to start stimulating our teams’ curiosity now, be open to looking at challenges through a new lens, leave room for experimentation, and foster a safe culture that tolerates the failure inherent in innovation. To move in the right direction, it’s our responsibility to define a clear vision and principles that support the development of these new solutions, starting with ensuring data security and transparently conveying the purpose of their use. We also need to thoroughly test what we’re going to put out on the street (not launch it just to make the brand look innovative) and have the honesty to focus our efforts on satisfying existing needs and solving the problems that most impact our clients and consumers.

 

This article was originally published in the winter edition of Líder magazine, with the theme The Touch of the Future. Online version here.

 

Related articles

Opinion Articles
RxRepository: Building a testable, reactive, network data repository using RxSwift (part 1)

In this series we will tackle the problem of optimizing network access to fetch data from the network, a common theme of networked applications. While it is certainly trivial to fetch data from a server in any modern framework or OS, optimizing the frequency of access to the network, in order to save bandwidth, battery, user frustration, amongst other things, is complex. More so if you want to reduce code duplication, ensure testability, and leave something useful (and comprehensible) for the next engineer to use.

Opinion Articles
RxRepository: Building a testable, reactive, network data repository using RxSwift (part 2)

In part 1 of this series we started tackling a common problem of networked applications, that of optimizing resource usage and user experience, by optimizing network access. We typically do that by avoiding expensive resource usage, as in avoid making network calls. This avoidance is not more than a mere compromise on the type of resource we decide to spare. Trade a network call for memory space, by caching network responses. It also comes with constraint relaxation, as we do not need the latest version of a particular resource. We, thus, avoid a network call. Nevertheless we want that what we have cached to eventually expire, or to be able to forcefully reload a resource.