UbiKann - Empowering Ubiquity

AI in my pocket

AI In my pocket

AI In my pocket

As discussed in the previous post, AI is a nascent and revolutionary technology. Why, well, it looks set to dramatically change and impact society, the economy and our jobs as we know them.

A leaked memo from Google gives us a glimpse of how even the major companies fighting for the top position may not be in such an enviable position as we thought. It also explains how many major IT and consultancy companies seem a bit lost, or at least on the back heel with their offerings.

One thing I take away from the leaked Google 'Jerry Maguire 2023 memo' is that as consumers we should, in the short to medium term, start seeing options on our own personal equipment. The resources needed for such "assistant and chat" AI systems may mean it first starts with powerful laptops before our smartphones have the appropriate hardware. Or it may be through hybrid versions that can manage certain things locally and offload more power hungry tasks to a server. Smartphones have several blockers including having the equivalent of several physical GPUs, as well as the memory wall for all the params that need to be readily accessible, an issue that servers don't have but all current smartphones would come up against.

As I manage servers myself, I could easily see myself creating a server part of a phone assistant, just for my family and I, for example. I'm sure some brilliant developers will think of ways to do this, whether it is hybrid or some other way. It's why the memo makes a lot of sense. While Google and OpenAI are in a battle for dominance. Wouldn't it be great if there was a 3rd option that was great for society as well rather than the just the Tech giants?

It also means that choosing the hardware on your phone may be more and more important. For example, few phones other than the Google Pixel have anything like the necessary hardware for some of these AI / Chatbot / Assistant etc functions. Even then, it is mainly for well-known functions like "voice to text". It is a sign Google has been working on these types of evolutions for quite some time, anticipating the required hardware.

After the timid market response with Google Glass, it would be understandable to imagine a lot more caution in unwrapping their AI tools to the public before they are ready. OpenAI launched theirs with far less regard for risks, 'à la Facebook', launch it as soon as possible and fix bugs asap.

I used Gmail shortly after it launched and I remember the beta label that lasted for years. You would have thought Bard could also have used the same beta label, you know, like OpenAI does!

Time will tell whether the leak of Llama developed by Meta and currently being used by several open source AI projects will end up giving Meta a considerable advantage compared to the closed door policy of Google and OpenAI. Google's research work over the past years that was shared through official publications was one of the key drivers of where we stand today with AI, notably this famous study from Google (pdf).

But in recent months, Google has overhauled its AI operations with the goal of launching products quickly, according to interviews with 11 current and former Google employees.

Google, like OpenAI, has changed gears in recent months, taking cues from one another in terms of major strategic decisions and roadmaps for AI related topics.

But as per the famous leaked memo, so too, have we seen passionate open source developers and other entrepreneurs diving into the opportunities AI promises.

There are already developers who have got Llama / foundation models to work on a Google Pixel phone, be it at 5 tokens per second.

The ability of a phone to provide hardware support for AI related functions and activities is going to become an interesting selling point. As per above it is unlikely that phones will be able to cover GPU needs and high memory capacity will also be an interesting plus.


Warning: Trying to access array offset on value of type bool in /home/ubikann/public_html/wp-content/plugins/amp-analytics/amp-analytics.php on line 65
Exit mobile version