• Breaking News

    Sunday, August 29, 2021

    Home Unlabelled Android Dev - What do you use except SingleLiveEvent for one time actions in MVI/MVVM?

    Android Dev - What do you use except SingleLiveEvent for one time actions in MVI/MVVM?

    August 29, 2021

    Android Dev - What do you use except SingleLiveEvent for one time actions in MVI/MVVM?

    What do you use except SingleLiveEvent for one time actions in MVI/MVVM?

    Posted: 29 Aug 2021 04:22 AM PDT

    I am trying to find something to replace SingleLiveEvents in my project, I used them a lot for one time actions such as toasts and error messages. But as you know SingleLiveEvents have a lot of drawbacks. Would be great to hear some real experience with SingleLiveEvent alternatives. Thank you.

    submitted by /u/Sensitive_Muffin_555
    [link] [comments]

    how to handle the scenario where the versions of Dependencies/MinSDK/CompileSDK/Kotlin Version/ Java Versions /.. etc OF A LIBRARY does not match with the project?

    Posted: 29 Aug 2021 07:53 AM PDT

    Hello there. I am trying to create my first library. I have a few questions.

    a library defines its own set of dependencies and minimum support sdks.

    so what is going to happen for people using my library in their apps with versions greater than/ less than what my library has defined? 1. Will my library crash because it is getting a version bigger / smaller version than what it required? 2. Will the user's app start to crash because my library is providing their app with versions of dependencies greater than/less than what their code had supported?

    1. What is the best solution to deal with either of these?
    2. This maybe not related, but How do libraries like Retrofit and jetpack libraries deal with these issues? Retrofit doesn't need an okhttp dependency, but if the app provide one, it starts using app's dependency. won't it break, if say app provided it with okhttp v1.0?

    for reference assume this is my library : a weatherView which automatically fetches weather info every 2 mins. its completely in kotlin and I define its java version as 11, min sdk version as 28 compile sdk as 28 and a requirement for material components v1.5 and kotlin v 1.6. who would be able to use this? for whom this is going to cause issues and on app side, or on my library's side?

    submitted by /u/appdevtools
    [link] [comments]

    Action button best practices? FABs and/or buttons?

    Posted: 28 Aug 2021 03:24 PM PDT

    Action button best practices? FABs and/or buttons?

    I realize this is very subjective, but I'm wondering what would be the best-practice approach to something like this.

    This is what I've come up with, but technically the Material guidelines say you shouldn't have more than 2 FABs per screen.

    \"Bad\" design because it uses more than 2 FABs.

    The primary action for my use is without question going to be the "Next" button to look at your next card. "Previous" and "Add new" are the next two most important actions. If I stick to only 2 FABs then one of these actions has to exist elsewhere, and I don't know where would be kosher.

    Alternatively, I wonder if THIS idea is technically fine, but it looks terrible compared to my "bad" one above.

    Alternative design

    Any advice? Or any suggestions what you think would look better and/or be within Android's guidelines?

    A more generic version of this question would be, what's the best way to represent 3 equally important actions on a screen?

    Thanks!

    ​

    EDIT: Based on u/xdebug-error's suggestion, this was my interpretation of the feedback. Thoughts on this?

    https://preview.redd.it/yv7qiuq5x6k71.png?width=371&format=png&auto=webp&s=ec3b2e8d20d948fe14434f7e0b99ce88383c1b00

    submitted by /u/MoraGames
    [link] [comments]

    I made a flutter app for Anime episodes and news updates. (Flutter)

    Posted: 28 Aug 2021 05:51 PM PDT

    Features

    More details here.

    Google Play | GitHub

    Under the hood.

    • Admob Integration.
    • Google Play In-app purchase.
    • Firebase Push Notifications
    • GitHub CI/CD for automated builds and upload to Google Play.
    • Nodejs + mongodb backend (closed-source for now).

    PS: The ads (Admob) are not working in production for now. I made a single mistake and google limited my AdMob account. Will try to resolve this in the future. The test ads do work perfectly fine though. Damn Google is too strict.

    submitted by /u/yurabe
    [link] [comments]

    Our user-generated football (social network where users publish their own content has been suspended and removed from Google Play due to alleged copyright infringement

    Posted: 28 Aug 2021 11:15 AM PDT

    Our user-generated football (social network where users publish their own content has been suspended and removed from Google Play due to alleged copyright infringement

    https://preview.redd.it/4g0vc97745k71.png?width=978&format=png&auto=webp&s=17c659b29f1484b4e61475d7bf0369b6df0d3d7e

    The guy who reported our app claims that our football app has some videos that violate the copyright, note that our app is a user-generated app, where users publish their own content and we don't own any content. and we have a terms and condition that states that clearly plus the fact that we ask our users to make sure they never upload any illegal content.

    we also have a report feature where anyone can report any content and we'll take it down.

    submitted by /u/Kilanyworld
    [link] [comments]

    Design to Dev - Font Size/scaling Issue

    Posted: 28 Aug 2021 12:29 PM PDT

    When designers design in 360*640 resolution (360 width) and share with developers, font size always GETS SMALLER after development (native android)

    ie, 16px font looks too small after dev. Kindly share your views and solutions to this

    productdesign #AndroidDev #figma #handoff

    submitted by /u/mujahid_96
    [link] [comments]
    Read more
    at

    No comments:

    Post a Comment