home.social

Search

58 results for “LeonOmelan”

  1. @LeonOmelan And it's making the app more "my own" for the users! 😊

    Sounds nice! I'm finishing the #CoffeeCollective on the picture, had that #MOK before and will start a washed #Kenya #Kiganjo from Czech roastery #Doubleshot on Sunday 😊 Happy.

  2. #Cofi is literally my favorite #app on my phone. It's made my brews way more consistent and the weight multiplier consistently saves the day for me when I want different amount a of coffee. 🤎 ☕
    Thanks @LeonOmelan for the wonderful app :)

    #android #androidApp #coffee #cofe #brew

  3. I had to disable the app of from the Google Play Store.
    Google wouldn't ship any updates to Cofi if I didn't implement Ongoing Activity into the wearOS app, even after disabling all of the code related to the notifications and working in the background.
    I don't have time right now to rewrite notifications and timer handling to include Ongoing Activity, and I needed to unblock Android app updates so that I could ship all the new features that I implemented since the last update.

  4. I had to disable the #WearOS app of #Cofi from the Google Play Store.
    Google wouldn't ship any updates to Cofi if I didn't implement Ongoing Activity into the wearOS app, even after disabling all of the code related to the notifications and working in the background.
    I don't have time right now to rewrite notifications and timer handling to include Ongoing Activity, and I needed to unblock Android app updates so that I could ship all the new features that I implemented since the last update.

  5. I had to disable the #WearOS app of #Cofi from the Google Play Store.
    Google wouldn't ship any updates to Cofi if I didn't implement Ongoing Activity into the wearOS app, even after disabling all of the code related to the notifications and working in the background.
    I don't have time right now to rewrite notifications and timer handling to include Ongoing Activity, and I needed to unblock Android app updates so that I could ship all the new features that I implemented since the last update.

  6. I had to disable the #WearOS app of #Cofi from the Google Play Store.
    Google wouldn't ship any updates to Cofi if I didn't implement Ongoing Activity into the wearOS app, even after disabling all of the code related to the notifications and working in the background.
    I don't have time right now to rewrite notifications and timer handling to include Ongoing Activity, and I needed to unblock Android app updates so that I could ship all the new features that I implemented since the last update.

  7. I had to disable the #WearOS app of #Cofi from the Google Play Store.
    Google wouldn't ship any updates to Cofi if I didn't implement Ongoing Activity into the wearOS app, even after disabling all of the code related to the notifications and working in the background.
    I don't have time right now to rewrite notifications and timer handling to include Ongoing Activity, and I needed to unblock Android app updates so that I could ship all the new features that I implemented since the last update.

  8. I'm having a lot of fun playing with Compose multiplatform. It looks like the fastest way to build an app for Android, Web, and Desktop all at once. Sure, it isn't as mature as + but it does require a lot less effort/boilerplate to start building the app.
    I need to check out what the iOS side looks like.

    I'm not sure I like that web version is compiled into

  9. Cool and all, but with requirements to pay Apple "technology fee" it still sucks for apps.
    I would be open to try and port to , but I don't want to pay anything for distributing the app on my own.

    9to5mac.com/2024/03/12/iphone-

  10. Cool and all, but with requirements to pay Apple "technology fee" it still sucks for #OpenSource apps.
    I would be open to try and port #Cofi to #ComposeMultiplatform, but I don't want to pay anything for distributing the app on my own.

    9to5mac.com/2024/03/12/iphone-

  11. Cool and all, but with requirements to pay Apple "technology fee" it still sucks for #OpenSource apps.
    I would be open to try and port #Cofi to #ComposeMultiplatform, but I don't want to pay anything for distributing the app on my own.

    9to5mac.com/2024/03/12/iphone-

  12. Cool and all, but with requirements to pay Apple "technology fee" it still sucks for #OpenSource apps.
    I would be open to try and port #Cofi to #ComposeMultiplatform, but I don't want to pay anything for distributing the app on my own.

    9to5mac.com/2024/03/12/iphone-

  13. Cool and all, but with requirements to pay Apple "technology fee" it still sucks for #OpenSource apps.
    I would be open to try and port #Cofi to #ComposeMultiplatform, but I don't want to pay anything for distributing the app on my own.

    9to5mac.com/2024/03/12/iphone-

  14. I would very much like to release a new version of , but issues with , and being blocked by Google for "not having WearOS" in full description hold me back.

    I have a significant number of users on the Play Store, so I don't want to abandon them on the old app version.

  15. I would very much like to release a new version of #Cofi, but issues with #Fastlane, and being blocked by Google for "not having WearOS" in full description hold me back.

    I have a significant number of users on the Play Store, so I don't want to abandon them on the old app version.

  16. I would very much like to release a new version of #Cofi, but issues with #Fastlane, and being blocked by Google for "not having WearOS" in full description hold me back.

    I have a significant number of users on the Play Store, so I don't want to abandon them on the old app version.

  17. I would very much like to release a new version of #Cofi, but issues with #Fastlane, and being blocked by Google for "not having WearOS" in full description hold me back.

    I have a significant number of users on the Play Store, so I don't want to abandon them on the old app version.

  18. I would very much like to release a new version of #Cofi, but issues with #Fastlane, and being blocked by Google for "not having WearOS" in full description hold me back.

    I have a significant number of users on the Play Store, so I don't want to abandon them on the old app version.