The selfengine UI is taking shape, at the heart screen is a live data section. Given the context set, live data will be visualized. Right now the visualization is a chart, one for the past and one a prediction for the future. Charts only come to life with data and the world records for each swimming stroke are going to be the starting point and then anyone using the selfengine can add their own personal data.
Add swimming strokes, distances and times
Select with context is live
Visualised records on past chart
Do some datamining/statistics to make future predictions. (should be fun)
The code has not been flying so fast this year on the LL OS project as I focus to apply it to the world of sport via the Open Sport Project. This is providing a niche focus with which to apply the lifestylelinking ideas. LifestyleLinking does not mean much to most folks straight off the bat so the best two world description would be to call the Lifestylinking Open Source Project as a Self Engine.
And a Self Engine produce suggestions. Much like a search engine provide results. I ve written a little more on the term on my blog.
The three biggest trend converging around this market are the quantified self movement, big data and the webs flipping back into decentralisation mode after its silo building phase again.
The Self Engine has a UI that allows the individual to manage their attention and context of their life, aggregation of data, hopefully the open source nature of the project will allow a data plug marketplace of tools both to include different data source and ‘data mining’ techniques, all this done in real time.
The LifestyleLinking Open Source Project has been ‘live’ for 4 years now, initially years of experimentation to get an application to perform ‘lifestylelinking’. That is to allow an individual datamine themselves and to connect them with the best personalized content given their view of the world(universe). How do these words translate into building a User Interface?
Good question. To explore this I have setup a page on Moqups, the LifestyleLinking m0qup. The starting concepts. Three blocks + Footer.
Identity Top block:
The expression of Identity. This gives the LL application a life-line into the digital assets that make up an individual. Hopefully, the Personal Data Locker / Service providers will have empowered all individuals with access to their own data.
LifestyleLinking Ingredients Display:
Given the identity information this needs to be visualised so that it can be use to construct the intention for the individual. Initially this will be a tagcloud / list of words extracted from their historical attention/identity.
With an intention selected (dragged into the LLflow area is the current UI model being pursued), ‘LifestyleLinking’ will be performed, this creates a social network between the individual and all other content based upon what they have authored in the past, given the current intention context, information will be displayed. Initially, blog posts.
A link to the LL open source project and a ‘clone ‘me’ ‘ link. A reminder that if the individual wishes then new applications can be spawned from this LL instance i.e. initially a link to github repository for developers to install their own LL application and in the future hosted online services complete with data flow.
Posted in Uncategorized
Tagged application, behviour, design, development, driven, interface, lifestylelinking, LL, open, source, start, thinking, UI, user
Over the last year or so I rewrote the lifestylelinking code in OOP PHP. This involved setting up object patterns, for me learning about pattern and then deploying those I sough fit. However, at the end of this process I felt the code was still to rigid for a data driven application. I have been following node.js for a while and have been encourage by some fellow coders that it well suited to this project. I agree with that conclusion. Not sure exactly how the node.js code will pan out but the potential it brings to some deep core problems should mean months of fun coding ahead.
The goal over the next 2 month is to get the code into a continuous integration and unit test framework. Probably Jenkins and PHPunit test. In the mean time those keen enough to download the code from GITHUB then please contact me and I will be more than happy to hand old you through the set up of the code.
The last post mentioned StrataConf.com 2011, we are now in 2012 and I am attending the event in Santa Clara, California. This is giving the opportunity to share the LifestyleLinking project and its ideas with the data science community. The way I have been describing the project is that is allows an individual to ‘data mine themselves and share the answers’. For example data mine your blog posts against Wikipedia definitions, but what definitions there is a lot to select from? The idea is to crowd source those from existing word clouds an individual has e.g. delicious social book marking list of words and match those to Wikipedia definitions. The + share part would them involves those individuals that want to share and thus gain a network effect by including the data mining ‘me’ results from other blogs giving the potential to reach more relevant data on topics of interest to the individual.