AI + HTML5 = The Future
A few days ago I wrote a blog post titled "Apps are so yesterday" where I shared how I envision intelligent devices of the future to be working. I only use the word "future" because no one has used our software development kit (SDK) to develop those use-cases yet. Our SDK allows web app developers to build these science fiction use-cases today and we will be releasing the SDK in about 3 weeks (so sign-up!).
But what's behind the SDK? I won't reveal everything in this blog post. Like to keep some stuff for the launch event. Instead I'll give you some idea on how and what we were thinking when we developed this technology.
We wanted to enable devices, apps, content and networks to automate how they connected with each other. We wanted content and software to flow and merge together without the user specifically requesting it. This means the networks and devices needed advanced enough intelligence to not only know what was going on in your life and the world in general, it has to actually comprehend that knowledge.
Imagine walking into a restaurant to meet with some clients over dinner and drinks. As you sit down you notice that your mobile device is showing a personalized menu on the screen, short bios of your clients, letting you know one client is running 10 minutes late and silences the phone for the duration of the meeting.
Using standard geo-fencing techniques you could easily invoke a restaurant app once you arrive the restaurant. But this is not a usual app unless there's a restaurant app out there that is designed to also show bio's and keep track of people (I've looked, couldn't find any). And call me crazy, but it makes no sense to build such an app. But in this scenario, such an app could actually be useful.
What our AI technology does is to go beyond knowing where you are. It works to figure out WHY you are there. In this case I'm there to meet clients over dinner. So it decides to invoke a standard restaurant app (which could have built by anyone). Through the SDK the app receives information about the menu content and how it applies to the user. More importantly, it also receives new code from various other apps and/or smart agents to handle the profiling viewing and late arrivals. All this information is received from invoking a single function within the SDK.
While what is happening behind the scenes are complex operations, we kept the interface to the developer of the restaurant app so simple that anyone can integrate AI into their apps. Here's the code to receive this intelligence (PHP):
$Nigel = new Nigel(); //Nigel is the name of the AI technology. This just creates a new Nigel object.
$menu = $Nigel->GetRestaurantMenu(); //In here you get a personalized menu for the restaurant and additional HTML/JS code
Once you have everything inside $menu (SimpleXML document) it is a breeze to go through it and decide how to present everything on the screen.
There really isn't anything else needed to receive this intelligence (besides including the SDK file of course). Once the "new Nigel()" is called, a connection to the neural network is created and your app becomes a new edge of this network.
Your app is now literally an intelligent piece of software. And that's what I believe is the future of technology. Artificial Intelligence + HTML5 (and other cloud languages like PHP) = future of software.
To learn more, please signup for our launch event. You can either come and enjoy pizza and beer downtown Portland or you can supply your own pizza and beer and join us via our web stream.
IAM | Okta | Cyber Security | ML | AI
9 年Interesting. Curious to explore SDKs.
Unix Engineer ve spole?nosti Commerzbank AG
9 年It's similar project like wearable smart watch instrument recognition in combination with GPS or Japan Sekai camera application architecture. https://www.youtube.com/watch?v=fpKDNle6ia4
Senior Advisor (Enterprise Data Management), Chief Information Officer (Semiconductor Manufacturing)
9 年Thank you for the additional detail. The legal questions are deeper than the implementations described. "Why" speaks to a person's "intent." Intent can be general or specific. Intent can also be for good or bad. "Intent" is a crucial component of criminal law and tort law. The "why" information collected begins to fill-in gaps in the chain of causation for specific-intent crimes and torts, which may be used in a courtroom in the future.
Senior Advisor (Enterprise Data Management), Chief Information Officer (Semiconductor Manufacturing)
9 年The "why" piece is curious. We can already answer "what" and "where" about a person and your plan is to extend it to answer "why." I assume that you have a plan to collect information through the SDK to further your work on developing the "why" capability. I also assume you have thought through how to safeguard the information as there are some legal questions that start to surface. Recollections of "This Perfect Day" by Ira Levin are coming to mind.
Cognitive Systems Architect
9 年Wonderful concept and powerful technology, I can't wait for the launch event!