HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
iSoron
uhabits
Kotlin2018–2026
iSoron / uhabits

uhabits

Loop Habit Tracker, a mobile app for creating and maintaining long-term positive habits

23Distinct people
25Mentions
2Explicit recommenders
10.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Loop Habit Tracker, a mobile app for creating and maintaining long-term positive habits

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love this app, I've used it many times in the past for tracking habits. Just want to point out that its also open source and available on F-Droid.…

jcul used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

Mentions over time

HN mentions by year25 dated mentions

Observed mentions: 2018-01-04 02:50:24 UTC to 2026-07-24 14:34:38 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 4 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC743
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

25 sources
If I were building a habit tracking app for iOS I wouldn't start from scratch. Even if I had a completely new take on the UI, I would try to reuse or adapt a data model from an existing app. The easiest way to do that would be to clone the repo for the open source Loop habit tracker: https://github.com/iSoron/uhabits and then ask Claude Code to study the data model and API, and help me think through what I need to add/change to support the features I want. Once the data model is in great shape, then let the AI go and build, test, iterate etc.
In I Tried Building a Real App with AI. It Took a Year
Mostly some version of GTD. A todo list managed by http://todotxt.org/. Items are dated and I make sure I review (remove or modify) items that have become stale. A similar list for non-actionable ideas (called inbox in GTD). I think I end up removing most of these. A text file with dated items for a "waiting for" list( e.g. waiting for an answer to a message), reviewed regularly. A list of "projects" (somewhat vague, but list priorities, reminds me of bigger goals). I don't really do "proper" project management for personal things, I guess I could, but the overhead would be too big for me to keep this consistent over time. A proper and reliable calendar. I use calcurse (https://www.calcurse.org/) as I like curse-based interfaces, it makes it trivial to use my setup via ssh. I'm always shocked when I find out some people don't really have
Read the rest
any calendar and just hope they'll remember appointments and events. It becomes obvious when they inevitably forget to show up somewhere and have to deal with the consequences. "Notable Plus" (https://f-droid.org/en/packages/com.icechen1.notable.pro/) for very quick notes on mobile (that I write down properly in one of the previous lists within 24h). Lately I'm also experimenting with some priority queue based on dates to make sure I do some things regularly. Let's say you do 5 different sports, and you want to do all of them (at the cost of doing any of them less frequently). You could keep track of the last time you did them, and to choose what to do next, you do the one you haven't done in the most time. There are few things I do once in a while, and when I do them, I often think "why didn't do that earlier", and I think this applies nicely to this when time is just limited. E.g. reaching out to people, going to some places... I edit most of these text files using vim, or Markor on Android (https://github.com/gsantner/markor). Shared via Syncthing on my personal devices. Automated version control via Git (meaning daily automated commits), although in practice I so rarely use this that I could get rid of it. I guess it's cheap so why not. A mobile app (https://github.com/iSoron/uhabits) to keep track of habits. At this point I have enough of them that doing them all in one day means I had a good day. That removes some thinking when I have little time and I'm not sure what I should do: just try to tick one more habit. Org-mode looks interesting but I've never managed to migrate to it, I suspect it's because I'm already too efficient with my current setup such that it's too much friction to switch to org-mode and spend months just reaching the same level with it. Overall whatever works for you, but I'd advise against proprietary apps and services: I've had about the same setup for about 10 years, I can't imagine how many productivity apps were created / deprecated during that time. It's very likely that my setup or a similar one will still work in 10+ years with very few changes required.
In Ask HN: How do you organize your life?
perfect example of foss accessibility issue: https://github.com/iSoron/uhabits this dev refuse to consider accessibility as it means ui changes or new option. users with visual impair are unable to use app and dev just locks issue reported for it and ignores users. probably to boost number of dls/markerting. even if user does a patch dev just closes and does his own thing that dont help. even foss projects kick contribs out for try to help
In Please don't use Discord for FOSS projects
dkoala223·Mar 15, 2021Submission

How to help accessibility without more option?

been watching some activity on a project, as i have the issue too, and maintainer doesnt want to merge pr or add options to improve accessibility to his app (link below). is this possible to do in a reasonable manner? visual issues are the subject here what also do you do in these cases about these people? somewhere like eff that can help? maintainer also attack the contributor for them having discussion about the issue too https://github.com/iSoron/uhabits/pull/848#issuecomment-798813704 here is more info but maintainer hid all comments even on topic ones to avoid bad publicity likely https://github.com/iSoron/uhabits/pull/777 and a user said they had eye issues and have trouble with light and dark mode and it got locked https://github.com/iSoron/uhabits/issues/843
2 points · Open discussion

GitHub discussions further gamify the platform

discussions gamify github like contribution graph. there are no counts for discussions like issues/prs so authors can hide issues by moving them. see for example: https://github.com/isoron/uhabits anything that isnt specific a crash is moved to discussions so it can be ignore. anyone see similar in other repos? doing this keeps issues low by hiding them so stars etc can be high. then author says they have only a few issues open for the project, and users see the same so think its probably good
2 points · Open discussion

Showing the 15 most recent of 25 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.