Android Dev - App Feedback Thread - August 22, 2020 |
- App Feedback Thread - August 22, 2020
- "Rate this app" functionality using In-App Review API
- ConstraintLayout 2.0.0
- Performance loss using compound components?
- Why can't you set an ActionMode bar's style programmatically?
- Turn off deprecation warning from Hilt compiled code
- Google releases Admob for Android
- How do apps handle Periodic Jobs in 2020 that work outside app, with latest android version limiting background functionality and OEM's prioritizing battery life over app functionality ?
- SQLDelight release with Kotlin Native 1.4.0
- Cursos en developer.android.com
- Learn Java REST API in 10 minutes (Web Service Coding Tutorial 2020)
- On average, how long does it take for your app release to get reviewed by Google?
- Android Play Store review time increased?
- Is there any good article for creating rest API for android app idea ?
App Feedback Thread - August 22, 2020 Posted: 22 Aug 2020 05:29 AM PDT This thread is for getting feedback on your own apps. Developers:
Commenters:
To cut down on spam, accounts who are too young or do not have enough karma to post will be removed. Please make an effort to contribute to the community before asking for feedback. As always, the mod team is only a small group of people, and we rely on the readers to help us maintain this subreddit. Please report any rule breakers. Thank you. - Da Mods [link] [comments] | ||
"Rate this app" functionality using In-App Review API Posted: 22 Aug 2020 02:46 AM PDT
| ||
Posted: 21 Aug 2020 06:04 PM PDT | ||
Performance loss using compound components? Posted: 22 Aug 2020 03:20 AM PDT Hey, so some time ago I discovered that we could create compound components by extending some kind of a ViewGroup and inflating an layout into it. After some time I noticed that I should use the merge tag as the top most tag in that layouts to prevent unnecessary nesting. Recently I saw a post that stated that nesting ViewGroups is very bad for performance and we should keep our view hierarchy flat. I 100% agreed with that. Finally my problem: I got in love with compound views as they make some components reusable (not only the layout but also some logic that is coupled to them - that's why I don't consider that include tag as satisfying as compound components) and reduce complexity as layout files get smaller and so on. But with every compound component you add to your layout, you add an ViewGroup that is nested. Sometimes this can introduce multiple layers of nesting (as an compound component could be used in another one). Now I would like to know how big the performance penalty is if I would like to continue compound views to split up my layout and if there is a way to eliminate the issue of nesting compound components? [link] [comments] | ||
Why can't you set an ActionMode bar's style programmatically? Posted: 22 Aug 2020 05:25 AM PDT ActionMode bars... is there ANY way to set the height or style via Java (not xml)???? If not, why hasn't this feature been added? I feel like this is really bad. I can't change every single ActionMode bar style via the theme just for ONE actionmode, specific situation. I need to add more room when there's a subtitle. [link] [comments] | ||
Turn off deprecation warning from Hilt compiled code Posted: 22 Aug 2020 02:39 AM PDT My gradle build system is set to stop when there are warnings on source files. Hilt generated code uses some deprecated call so my build miserably fails For now I allow to compile with warnings but the question is (drum roll): Is it possible to turn off deprecated warnings coming ONLY from generated code (specifically Hilt)? [link] [comments] | ||
Google releases Admob for Android Posted: 22 Aug 2020 03:02 AM PDT Google has released Admob app for android and looks like they are using Flutter for this just like they did with Goohle Ads app. What are your thoughts on this? [link] [comments] | ||
Posted: 21 Aug 2020 04:51 PM PDT | ||
SQLDelight release with Kotlin Native 1.4.0 Posted: 21 Aug 2020 07:38 PM PDT
| ||
Cursos en developer.android.com Posted: 22 Aug 2020 06:54 AM PDT
| ||
Learn Java REST API in 10 minutes (Web Service Coding Tutorial 2020) Posted: 22 Aug 2020 01:39 AM PDT
| ||
On average, how long does it take for your app release to get reviewed by Google? Posted: 22 Aug 2020 01:05 AM PDT On average, how long does it take for your app to get reviewed by Google when creating a release? Earlier this year I published a puzzle game app, which is rated family friendly, and I would say on average it takes 2 - 3 days for a review. Sometimes a bit more or less. If I discover a bug after a reviewed app release, and in my experience if I am fairly quick in releasing a fix for this, it gets reviewed and approved within the same day. Unfortunately, my last app release has so far been waiting for a review for 3 weeks. I created the release on August 1. The release contains a bug fix for a release which was reviewed and approved one day prior. I also changed the text in the store listing slightly on August 2, which is still waiting for approval as well. I getting some feedback about the bug from users, and I also have another release (accessibility and app linking) ready to go, so it is becoming a bit frustrating waiting for this review. I am wondering if my case is extreme or have any of you had the same experience as me. Thanks :) [link] [comments] | ||
Android Play Store review time increased? Posted: 21 Aug 2020 01:06 PM PDT Hey all. My dev team and I have been making regular updates to our app in the play store about once a week throughout the entire year, and despite the notice that Play Store review times will take longer, every app update went live in a few hours. Until now. Suddenly, it's been EIGHT days since our "Full Rollout" to production (and three days ago we did a beta Rollout). Neither the production rollout nor the beta rollout has gone live. Android support states that this is normal and the reviews are simply taking longer than usual. However, going from 3 hours to 8+ days seems pretty drastic. We did notice that the Android build we uploaded for the production rollout had some sort of "outdated Android SDK version" warning which we hadn't seen before. The build is using SDK version 28. We're wondering if this might be the true culprit. Android support has warned us not to upload another build as it will reset the review process, so we've avoided doing that thus far. Is anyone else seeing a similar issue? Could the API version warning be the true culprit? EDIT: So I just discovered this: https://developer.android.com/distribute/play-policies#:~:text=Apps%20must%20target%20API%20level%2029&text=By%20November%202%2C%202020%2C%20all,the%20API%20level%2029%20requirement. It appears that the min. target SDK version is now 29. I'm guessing that's the culprit. We're going to try upgrading our target SDK to see if this gets the app approved faster. EDIT 2: It turns out min target SDK 29 won't be enforced until November 2020 for existing apps. [link] [comments] | ||
Is there any good article for creating rest API for android app idea ? Posted: 21 Aug 2020 07:53 PM PDT |
You are subscribed to email updates from Developing Android Apps. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment