We would want to have login functionality but the app features shouldn't depend on that. So, if a user logs in, he gets a personalised experience with his custom settings but if he doesn't login he gets to see all the basic information and features like talks, bookmark sessions etc.
@brainbreaker Please feel free to make a proposal. Integrating this feature should be done later, when there are use cases implemented as well though.
@mariobehling @mananwason Can i work on this??
Not required yet because server doesn't support it. Cheers!
On Mon 16 Jan, 2017, 7:41 PM Saket Kumar, notifications@github.com wrote:
@mariobehling https://github.com/mariobehling @mananwason
https://github.com/mananwason Can i work on this??—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-android/issues/363#issuecomment-272870851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFKCT4DG8daxxfZWhSErxHNtkqCbUksks5rS3p2gaJpZM4IgtuF
.>
Regards,
Manan Wason
4th year, B.tech - CSE
Indraprastha Institute of Inf. Tech. (IIIT) Delhi
Okhla, Phase-III, New Delhi-110020, INDIA
Website: www.mananwason.me http://www.mananwason.me/
can this be done using FireBase?
@Dipendra, I don't think firebase is the way to go here. All our data comes
from the JSON fetched from open-event server. It is not gonna be useful
unless we host our JSON database on firebase as well. The server has to
have the API to support G+/FB authentication.
On Tue, Feb 28, 2017 at 6:59 AM, Dipendra Singh notifications@github.com
wrote:
can this be done using FireBase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-android/issues/363#issuecomment-282913041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJE8R8JBR3lh6H-48se5vDejO-DQTFc_ks5rg3iPgaJpZM4IgtuF
.
@mananwason Please reopen this issue :smile:
@Shailesh351 As there is quite a bit of work about storing of the token and revalidating it to check if it is expired or not, you can check the Orga App implementation and reuse code from it. It is quite modular :smile:
@Shailesh351 also ensure all user authentication related features are toggle-able. That is we should be able to generation a version of the app that doesn't have any user authentication related features or features that need user authentication. We want give an option of a completely offline app too to the users.
It would be best if this requirement is taken into consideration from the very start of this.
@niranjan94 Sure!!
Most helpful comment
@Shailesh351 As there is quite a bit of work about storing of the token and revalidating it to check if it is expired or not, you can check the Orga App implementation and reuse code from it. It is quite modular :smile: