-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some questions and suggestions #2
Comments
Hello |
Features to implement:
|
I tend to think that anybody who is likely to want to use this software will also definitely be using the main nextcloud application. That being the case, you should NOT be implementing anything with respect to Android accounts api, rather instead you should use Nextcloud's SSO and process everything using Nextcloud API, otherwise you are definitely doing things the hard way. The way the authentication process works using SSO is such that on application launch, if an account has not been added to YOUR application already, it would call the Nextcloud SSO API, which would present a list of nextcloud accounts that have been configured on the device. User clicks the desired account, it prompts for confirmation, and you're done. |
Yes, I completely agree with you. But I thought that the SSO provided by Android itself(just haven't read the docs yet), so this why I wrote about Android API. |
I see nextcloud login preliminary support listed on beta 1.10 and cannot find how to test it yet |
You need to get the latest beta(i.e. 1.0-beta10) installed. Since F-Droid build takes from 3 days to a week, you should take this apk from releases page. To install it you will need to delete previous version(since it is signed by F-Droid key, warning: this will reset all in-app settings) and then after installing 1.0-beta10 from apk file you can open the app and press "Log in via Nextcloud app" and app should show Nextcloud's account selection dialog. |
F-Droid release of 1.10 beta is available as of today. Thank you. |
All features which were requested in this issue were implemented as per 1.0-beta12, so I am closing this issue |
Hey, I just saw your project on F-droid and was happy to see an alternative to the NC's default dependency on FCM.
Am I correct to guess that you currently poll every few seconds to fetch notifications ? It would be nice to know the average battery consumption on a typical day.
How does your app deal with connection breakages;
I currently use this developed by @ASerbinski. It uses server side events instead of polling. It's a bit more advanced to setup but barely uses any battery (like <1% per day) and I receive notifications almost instantly with no delay.
Some suggestions:
The text was updated successfully, but these errors were encountered: