Solodroid Blog

As we know, some of our products use the Blogger API service, in this article we will explain the limit on the number of Blogger API accesses per day. Blogger API has access limit of 10,000 request (list/search/get) per day, with the limit of 100 request per 100 second for each unique IP address. If my application has many users and exceeds the limit, then what? Unfortunately, this daily limit cannot be increased since Google doesn't provide premium or paid services package to increase the limit. So what's the solution? This is a daily limit, so the limit is only for one day and the limit will gone the next day, and so on. Then, is there any other alternative? Yes, in our application, Blogger API Key is managed from JSON file for remote configuration, if your application reach the daily limit, you can create new API Key using different email address and update your Blogger API Key with your new Key from the JSON file remote configuration. JSON file for remote configuration can

Ad network integration from IronSource, especially for banner type ads, for us is not optimized and it's not friendly for developers or publishers, the reason is because banner can only be displayed once and in one activity, while, our application have multiple activity screen like main screen activity, detail activity, posts based on category activity, search activity, etc, so, this is more than one activity. For example, if the banner ad is displayed on the main screen activity, this means that the banner ad will not be able to be shown in other activities, moreover, the banner ad also cannot be displayed again when we close the application and reopen it even on the main screen with note before the banner is destroyed first. According to official documenation in the banner ad integration section, before switch to other activity, banner ad must be destroyed first to make it can be loaded in the other activity, but, a destroyed banner can no longer be loaded, if we want to serve it

To run Admin Panel of Solodroid Products, web hosting that you use must have the following requirements : PHP Version 5.4, 5.5, 5.6 or 7.2 Support MySQLi and PDO Apache Server Shared hosting with Cpanel (We didn't check the script’s performance on the VPS and VDS hosting) Because this documentation using cpanel, a web hosting with cpanel is recommended. If you don’t have web hosting or domain, you can check on this sample site which provide hosting and domain service : Free web hosting & domain services : 000webhost ​ Premium web hosting & domain services (Highly Recommend) : ​ Hawkhost ​ ​ Hostgator ​ ​ Domainesia (Indonesian Hosting)​ Niagahoster (Indonesian Hosting)

 All the Envato Market Licence for single end products. The difference between Regular and Extended Licence is in terms of usage, Regular Licence for non-commercial needs (personal usage) and Extended Licence for commercial needs. As per Envato rules, you must purchase the app under an Extended Licence if : You plan to sell your own version of this app as a PAID app on the Google Play Store or other similar App Store You plan to make application to your client You plan to sell your own version of this app ( build app) on Flippa and similar markets

If you got this warning message when you publish your application on Playstore : This App Bundle contains Java/Kotlin code, which might be obfuscated. We recommend you upload a deobfuscation file to make your crashes and ANRs easier to analyze and debug Seems like it's a warning message coming from the new play console. Choose APK instead Android App Bundle https://prnt.sc/vcz3nb Or you can solve it just by setting your minimum api level to 29 https://prnt.sc/vcz16g

Sdk implementation has been following the official documentation correctly : https://developers.google.com/admob/ump/android/quick-start Creating consent message for apps in the funding choices account also has been following the instruction correctly : https://support.google.com/fundingchoices/answer/9794285?hl=en&ref_topic=9437574 We think this issue coming from the ump sdk for eu consent itself : https://groups.google.com/g/google-admob-ads-sdk/c/QWnSRYhmQ5g?pli=1 In regards to the questions that are asked, I agree with what was said and would suggest that if someone is concerned about UMP, that they are still fully able to use the legacy versions of our consent as that is still valid, to use legacy versions of eu consent, it can be configured from Config.java file. public static final boolean USE_LEGACY_GDPR_EU_CONSENT = true; If still no luck, you can post your question to get answers from Google Support Team : https://support.google.com/admob/thread/new?hl=en