I just checked all APIs/Libs that the app uses had declared support of API_LEVEL_28, but have recommended a higher target (above 30). My bad. I assumed this modern Material 3 Compose had hard API-level requirements.
Well, you are right about the audience, many people might prefer to downgrade to older versions. However, support of older versions will significantly complicate the development.
The app uses several APIs that are not available on older versions. In one moment in time when I had the support of lower versions the app consisted of many wrappers for OS API versions. It was a challenge to support and add new features to such a codebase.
Making it work in the long term is going to be a challenge. I agree.
I'm planning to implement as much tooling as possible so you can deal with annoyances that appear over time. While incentives can be outside of the app. For instance, there is an initiative called OfflineDay. https://www.reddit.com/r/OfflineDay/
And even now in-app, you can create a nudge for OfflineDay
That app I mentioned also had iOS version as well. I don't know how they made it, because AFAIK any customisation to unlock/lock process weren't allowed on iOS from the very beginning.
But nevertheless. It's a bit disappointing that major operating systems are becoming more closed for developers to create such beautiful apps
You also can try setting nudge Cooldown. It will prevent nudge from popping up during Cooldown period. For now it's 3 minutes max, but I can easily add more options in next release.
Yes. App already has a setting call Cooldown. It allows to have time after phone lock during which the app won't pop-up again. Not sure if that's what you are suggesting, and it's max time right now is 3 minutes.
I can relate to this. I conducted UX experiment during my Master's in Human Computer Interaction which was testing an impact of various interventions to screen time and user perception. I observed very similar pattern, if it clicks it stays with the people. Of course the experiment was with small group, but still.
A good comparison I think are "self help" books. People are still reading them and those books are really helpful during certain times. While same ideas and concepts are circulating across those books.
I believe such kind of apps and software deserve to exist. Whatever helps people to make their lives better.
That sounds nice. In my case, I rely heavily on many "essential" apps that are available on smartphones. Maybe the approach of having another Kale phone and a "Junk" phone is a thing (https://x.com/george__mack/status/1681378342627311640). And Punkt will be a great candidate for Kale phone.
The original app was released ~ 4 years ago, but it survived several rounds of overhauls from scratch while keeping the original idea - "showing nudges after phone unlock". It can be considered a launch because it's almost a remade app.
But as soon as I think about implementation I realize how complicated it is to make such an intelligent system that would understand intent and based on intent adapt the action. In theory, it all can be manually connected, but then it would require a complicated setup.
Of course, it's only from an implementation perspective. From the UX it can be trivial.
I even remember in 2019 finding an app that was using a popup after unlock to learn words of a foreign language, unfortunately, it closed and I cannot recall the name.
I'm thinking also about adding an option to have like 50% chance of a popup or a 75% chance, so it's less predictable. I first made it as every 2nd, 3d and so on, but maybe adding a randomness to it will be better? WDYT?
BTW, it was quite complicated but I added support for flip phones as well. So the app works correctly on flip phones as well. Flip phone users might have an ultimate setup.
Interesting. How are you dealing with cases when you need a navigation like Waze or Google Maps? Navigation apps are my main obstacles for trying a "dumbphone".