[foaf-protocols] Foaf-browser-app

[Natanael Arndt]

Hey Henry,
thank you for checking out our App and for all the good comments.

For the frinding issue: you might want to click the button titled "MENU" 
(left to the back-arrow button) it will show you the frinding function 
and a "home"-button.
The frinding function will use ping back in the future. At the moment 
SPARQL/Update and FOAF+SSL is used.

The First-Run wizard definitely has to be improved and I like the idea 
with the browser very much.

Through the menu you can also get to the preferences and change the 
WebID if you entered it wrong.
(The Menu button might be a general problem of Android but it will be 
changed in the Android UI starting from 3.0)

You might also take a look at the Contact synchronization, which 
integrates your contacs in your address book, from where you can use the 
phone number, email, jabber, ...

The "Browser" function should let the user find WebIDs by entering a 
search term but because there is still no usable WebID-Search-Engin we 
implemented it as a simple WebID input field.

Thank you very much
Natanael

On 04.10.2011 21:02, Melvin Carvalho wrote:
> On 4 October 2011 20:04, Henry Story<henry.story at bblfish.net>  wrote:
>> While playing with the very cool Foaf-browser Android application [1], I noticed that there are a couple of things that we need to standardise to make that type of application seamless.
>>
>> As it requires having an Android phone which not everyone may have, I put together a little video of the Foaf-browser here
>>
>>    http://vimeo.com/30014844
> Thanks, I got quite a lot out of that.
>
> Quite close to being able to see what the foaf cloud is capable of, on
> the mobile web.
>
> Agree that it would be good to recognize pingback:to and then add
> extra functions, such as friending.
>
>> where I also go into detail in some of the things that need to be improved, as I show how it works.
>>
>> 1. SEAMLESS STARTUP
>> ===================
>>
>> In order to allow seamless startup, there has to be a way for a user once he has installed the browser to find his home page.
>>
>> We discussed this yesterday on the WebID-XG incubator group meeting with Tim.
>>
>> a. getting to the home page
>> ---------------------------
>>
>> Clearly getting to the home page of the user is going to be important. That will require him to either:
>>
>>   - know his profile url
>>   - the company he is with to have implemented something like web finger, so that one could just ask him for his email address
>>   - ..
>>
>> We seem to have a few protocols to help here. What clearly was missing was the keygen equivalent for an application like that.
>>
>> b. keygen form pointer
>> ----------------------
>>
>>   We need  some way to get the equivalent of a keygen form in rdf. Then a non html browser could know where it needs to send an html POST of a keygen like response. Any ideas how to do this?
>>
>> 2. EDITING
>> ----------
>>
>> I suppose the RW community group have some idea of what is needed to allow such a tool to become an editor.
>>
>>
>> Henry
>>
>>
>> [1] http://code.google.com/p/mssw/wiki/Screenshots
>>
>>
>> You can run it in a emulator - very slow btw, but if you don't want to buy a phone it saves money.  Here is what I learned looking at it: The running stable release of the Address Book is
>>
>> http://code.google.com/p/mssw/downloads/detail?name=mssw-0.9.6-stable.apk
>>
>> The emulator can be found here:
>>
>>   http://developer.android.com/guide/developing/devices/emulator.html
>>
>> Once installed the tools/android  tool allows starts a GUI which allows one to create a virtual device. Perhaps one first has to install android 2.3.3 which is more like a phone, and create a virtual device for that. Then can launch the device. One installs the app on the virtual phone using once it is running
>>
>> ../platform-tools/adb install mssw-0.9.6-stable.apk
>>
>> (there may be a GUI way of doing that)
>>
>>
>> [2] this is true for creating WebIDs, for loving in and so on....
>>
>>
>> Social Web Architect
>> http://bblfish.net/