Features
- Change when we trigger the Updates request for the first time
- When the user arrives in Aptoide through the APKFY flow, we would make the Updates request in background to show the number of updates the user has to do to their apps. This was often looked as a hook for him to explore Aptoide's updates feature and to generate more downloads. We know the notification is not very efficient, probably due to the nature of the APKFY flow. Users come and install the app, they go out. This would cause a lot of pressure on our webservices, since every user would be making this request as soon as they enter the app. We changed it so it only is made when the user actually goes to the Apps bottom navigation menu. We kept the dot indicator on top of the Apps menu for the initial session.
Bug Fixes & Improvements
- Remove duplicate request to refresh updates that would happen in some situations.
- Support more Aptoide Website patterns to avoid issues in the future.
Issue references in JIRA
[Updates]
- APP-139: Change when we trigger the Updates request for the first time - https://aptoide.atlassian.net/browse/APP-139
- APP-144: Remove duplicate request to refresh updates - https://aptoide.atlassian.net/browse/APP-144
[Quality]
- APP-190: Support more Aptoide Website deeplinks - https://aptoide.atlassian.net/browse/APP-190
- APP-270: Settings issue - Legal deeplink - https://aptoide.atlassian.net/browse/APP-270