You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was reading (and trying to implement something) about integration with other SDKs (such as facebook's) before writing this down.
Due to the external auth process, I think that allowing the user to select multiple networks will make the whole procedure more complicated, UX-wise, thus I'm removing the checkboxes.
Generally, selecting one of those accounts will lead the user to an external auth dialog, which will return back a response code and an auth token, in case of success. In case of errors (SDK exceptions or connectivity issues), we could display a toast containing the error description and then go back to the first screen.
This activity should be launched from the action bar, and the back button, as expected, should get the user back to the main activity.
Currently, since we're using the generic channel fragment, the user has to click on the channel and then follow it, but I've got nothing against adding a follow button beside the channel item.
Are you proposing to write oauth providers for Twitter, Facebook and
Google? (and others in the future?) Do you think users are going to trust a
random app with their google password? I'm not convinced.
Path was hammered for uploading the entire address book in cleartet -
Your interface will also need to handle telling the user that we don't
upload their address book in cleartext/just hashes.
The SDKs provide their own auth implementations, so we don't need to
reimplement the auth process, it's just a matter of integrating them. And
we don't handle passwords, the auth process redirects the user to the
network's login activity, eg.: com.facebook.LoginActivity.
I was going through StackOverflow answers regarding using the
AccountManager vs. other networks' SDKs, and the majority leans towards
using the SDKs:
Are you proposing to write oauth providers for Twitter, Facebook and
Google? (and others in the future?) Do you think users are going to trust a
random app with their google password? I'm not convinced.
Path was hammered for uploading the entire address book in cleartet -
Your interface will also need to handle telling the user that we don't
upload their address book in cleartext/just hashes.
IMHO your first version should a) use the address book b) use the
account manager
Activity
abmargb commentedon Jan 14, 2014
Aim
Assumptions
Tasks
Flow
Main flow
MainActivity -> Friend finder activity -> MainActivity
Inside activity flow
Show network list -> Show channel list -> Finish activity
imaginator commentedon Jan 14, 2014
Please also detail how you propose the UX for this to work.
abmargb commentedon Jan 16, 2014
https://buddycloud.mybalsamiq.com/projects/android/Friend%20Finder%20Screen
imaginator commentedon Jan 17, 2014
Have you considered:
follow it)
do you choose to not do this?
On 16 January 2014 22:22, Abmar Barros notifications@github.com wrote:
Simon Tennant | buddycloud.com | +49 17 8545 0880 | office hours:
goo.gl/tQgxP
abmargb commentedon Jan 17, 2014
I was reading (and trying to implement something) about integration with other SDKs (such as facebook's) before writing this down.
Due to the external auth process, I think that allowing the user to select multiple networks will make the whole procedure more complicated, UX-wise, thus I'm removing the checkboxes.
Generally, selecting one of those accounts will lead the user to an external auth dialog, which will return back a response code and an auth token, in case of success. In case of errors (SDK exceptions or connectivity issues), we could display a toast containing the error description and then go back to the first screen.
This activity should be launched from the action bar, and the back button, as expected, should get the user back to the main activity.
Currently, since we're using the generic channel fragment, the user has to click on the channel and then follow it, but I've got nothing against adding a follow button beside the channel item.
I've updated the mockups to comply with this discussion:
https://buddycloud.mybalsamiq.com/projects/android/Friend%20Finder%20Screen
imaginator commentedon Jan 17, 2014
Good update.
Google? (and others in the future?) Do you think users are going to trust a
random app with their google password? I'm not convinced.
Your interface will also need to handle telling the user that we don't
upload their address book in cleartext/just hashes.
account manager
https://developer.android.com/reference/android/accounts/AccountManager.htmlto
match the account name (hash thereof)
abmargb commentedon Jan 17, 2014
reimplement the auth process, it's just a matter of integrating them. And
we don't handle passwords, the auth process redirects the user to the
network's login activity, eg.: com.facebook.LoginActivity.
AccountManager vs. other networks' SDKs, and the majority leans towards
using the SDKs:
http://stackoverflow.com/questions/4593061/how-to-retrieve-an-facebook-authtoken-from-the-accounts-saved-on-android
http://stackoverflow.com/questions/12972760/retrieving-auth-token-for-facebook-account-configured-in-mobile-via-account-mana
On Fri, Jan 17, 2014 at 2:03 PM, Simon Tennant notifications@github.comwrote:
Abmar Barros
MSc in Computer Science from the Federal University of Campina Grande -
www.ufcg.edu.br
OurGrid Team Leader - www.ourgrid.org
Buddycloud Dev - www.buddycloud.org
Paraíba - Brazil
imaginator commentedon Jan 17, 2014
Same for Twitter and Google?
Please add this flow to the dev Readme so that it's clear for other client
developers.
S.
First bits on #142. Working facebook integration.
imaginator commentedon Jan 18, 2014
this is "nobody"
book to invite friends in.
On 17 January 2014 18:30, Simon Tennant simon@buddycloud.com wrote:
Simon Tennant | buddycloud.com | +49 17 8545 0880 | office hours:
goo.gl/tQgxP
abmargb commentedon Jan 18, 2014
work differently as long as we don't handle the user credentials (login,
password). I've written a ContactMatcher interface
https://github.com/buddycloud/buddycloud-android/blob/master/src/com/buddycloud/fragments/contacts/ContactMatcher.javathat
abstracts that logic.
written as soon as this is ready.
On Sat, Jan 18, 2014 at 5:22 AM, Simon Tennant notifications@github.comwrote:
Abmar Barros
MSc in Computer Science from the Federal University of Campina Grande -
www.ufcg.edu.br
OurGrid Team Leader - www.ourgrid.org
Buddycloud Dev - www.buddycloud.org
Paraíba - Brazil