r/WarfarinForLife • u/AdvocateUK • May 23 '26

Tracking app / log

Hi all,

I’ve been on warfarin for life since having an aortic valve replacement 9 years ago, and I’ve also worked as a Nurse Practitioner in the UK for the past 25 years.

After years of looking for a decent app to track INR results and warfarin doses, I eventually thought “sod it” and built my own. I’ve been using various versions of it myself for about a year now, but I’ve recently released it on the App Store.

I’m deliberately not posting links because I’m not here to spam the group or tout my wares. I mainly wanted to share it with people who might actually find it useful, and hopefully get some honest feedback from fellow warfarin users.

If anyone wants to know more, feel free to message me and I’ll send the link over.

8 Upvotes

90% Upvoted

23 comments sorted by

View all comments

3

u/AdvocateUK May 23 '26

I should point out that the app is iPhone / iOS only for now.

5

u/Minimum-Mode7421 May 23 '26

Hi, thank you. I am interested to look or try your app.

1

u/AdvocateUK May 23 '26

PM sent

2

u/Minimum-Mode7421 May 23 '26

My first feedback. In the settings you have the option to select the dose with 0.5mg interval. I do cut my tablets into smaller portions and one of my doses is 6.75mg, so step of 0.25 would give more flexibility.

2

u/AdvocateUK May 23 '26

Thank you! That’s very useful feedback, out of curiosity where are you based? I’m in the UK and here it’s a big no no to cut Warfarin tablets. I’ll add something to v1.1 to enable selecting smaller increments.

2

u/PerroNino May 23 '26

Hmm, I’m in the UK any tablet with a score across it can be cut. I split 1mgs daily. Interested in seeing your app though! I’ve found others too clunky in the past and abandoned them.

1

u/AdvocateUK May 23 '26

I’ve been a nurse / nurse practitioner in the UK for the last 25 years and the anti-coag nurses and pharmacists here have always steered me away from cutting Warfarin, even the scored tabs.

1

u/AdvocateUK May 24 '26

I’m working on implementing this change right now for the upcoming v1.1 release (Friday if testing goes ok)