---
title: "Anurag Thakur (@devanuragt) | Hashnode"
description: "Sharing my GSoC 2026 joruney at LibreHealth. Read the latest articles by Anurag Thakur on Hashnode."
url: "https://hashnode.com/@devanuragt"
---

@devanuragt

# Anurag Thakur

@devanuragt · Mumbai, India · Joined May 2026

Sharing my GSoC 2026 joruney at LibreHealth

### [GSoC 2026 Final Report: Building Offline Sync for LibreHealth NeoRoo](https://devanuragt.hashnode.dev/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo?utm_source=hashnode&utm_medium=feed)

For my GSoC project this year, I spent the summer contributing to NeoRoo under LibreHealth. It's an app built for nurses doing Kangaroo Mother Care in NICUs to log baby vitals and send that data to DH

3 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo?utm_source=hashnode&utm_medium=feed)

[Aug 20](https://hashnode.com/posts/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo/6a878ed8f496f804d9662862)

### [GSoC 2026 Week 12: Fixing the last background sync bugs](https://devanuragt.hashnode.dev/gsoc-2026-week-12-fixing-the-last-background-sync-bugs?utm_source=hashnode&utm_medium=feed)

Last week was mostly about fixing bugs. I found two problems: sometimes the app created duplicate records during background sync, and sometimes the background engine crashed. Both only happened someti

1 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-12-fixing-the-last-background-sync-bugs?utm_source=hashnode&utm_medium=feed)

[Aug 10](https://hashnode.com/posts/gsoc-2026-week-12-fixing-the-last-background-sync-bugs/6a79b78550fcfa150c43929e)

### [GSoC 2026 Week 11: Background sync without burning battery](https://devanuragt.hashnode.dev/gsoc-2026-week-11-background-sync-without-burning-battery?utm_source=hashnode&utm_medium=feed)

Last week I finished the iOS side of the sync bridge, so Flutter now sees the same behavior on both Android and iOS. This week I moved into background synchronization, which is the part that matters m

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-11-background-sync-without-burning-battery?utm_source=hashnode&utm_medium=feed)

[Aug 3](https://hashnode.com/posts/gsoc-2026-week-11-background-sync-without-burning-battery/6a701eb75aa9de15d57d56cc)

### [GSoC 2026 Week 10: iOS sync is finally taking shape](https://devanuragt.hashnode.dev/gsoc-2026-week-10-ios-sync-is-finally-taking-shape?utm_source=hashnode&utm_medium=feed)

Last week I finished the Sync UI and Conflict Logs screens, so the app now has a much clearer way to show what is happening in the background. This week I started the native iOS sync bridge, which is

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-10-ios-sync-is-finally-taking-shape?utm_source=hashnode&utm_medium=feed)

[Jul 26](https://hashnode.com/posts/gsoc-2026-week-10-ios-sync-is-finally-taking-shape/6a662058dd29d77b000f01ca)

### [GSoC 2026 Week 9: Making sync visible in the app](https://devanuragt.hashnode.dev/gsoc-2026-week-9-making-sync-visible-in-the-app?utm_source=hashnode&utm_medium=feed)

Last week the backend side moved forward a lot. The server-wins conflict strategy is in place, and anything that cannot be safely merged is preserved in a local conflict\_log so it is not lost. The Syn

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-9-making-sync-visible-in-the-app?utm_source=hashnode&utm_medium=feed)

[Jul 20](https://hashnode.com/posts/gsoc-2026-week-9-making-sync-visible-in-the-app/6a5e1bf445e682b91ed68e3f)
