An automated insulin delivery app for iOS, built on LoopKit
1.7k
Stars
1.4k
Forks
71
Open issues
30
Contributors
AI Analysis
Loop is an open-source iOS app template for building automated insulin delivery systems, designed specifically for people with diabetes who want to implement artificial pancreas functionality on their own devices. It is highly experimental, not FDA-approved for therapy, and serves a specialized community of diabetes patients and developers willing to undertake significant technical and medical responsibility; it is not suitable for general users or those seeking a commercial, regulated solution.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Open-source automated insulin delivery app for iOS, built by and for the diabetes community
Loop is an experimental iOS app template for closed-loop insulin delivery, built on the LoopKit framework. It is developed and maintained by a community of people with Type 1 diabetes and serves users who wish to build and deploy their own automated insulin systems. The project explicitly disclaims approval for therapy and operates in a unique position: not a commercial medical device, but relied upon by a dedicated user base for daily diabetes management.
Loop originated in 2016 as a community-driven response to the lack of approved automated insulin delivery options in the US. It builds on LoopKit, a modular framework for glucose monitoring and insulin calculation. The project has sustained a core developer and user community for a decade, operating in regulatory and ethical gray zones while maintaining active development.
Star count (1,688) and fork count (1,417) have grown modestly but steadily over 10 years, reflecting a stable but niche user base rather than explosive adoption. The project has not pursued mainstream visibility; growth appears driven by word-of-mouth within the diabetes technology community and by ongoing technical maintenance. Recent push activity (June 2026) and modest star gains (5 in 7 days) suggest continued, slow-burn engagement rather than acceleration or decline.
Adoption not formally verified in README, but the existence of a dedicated Zulip community, a separate detailed documentation site (Loop Docs), and a Wiki with contribution guidelines strongly suggests an active user base. The project's longevity (10 years), continuous maintenance, and community infrastructure are indirect but substantial signals of real-world reliance. However, quantitative usage metrics (e.g., active installations, user counts) are not publicly documented.
Based on README, Loop is an app template built on LoopKit frameworks, which provide data storage, retrieval, calculation, and UI boilerplate. The app integrates iOS and watchOS interfaces for glucose monitoring, bolus entry, carb logging, and automated insulin delivery control. Appears to follow a modular architecture via LoopKit dependencies, but actual code structure is not detailed in README.
Not documented in README. No testing framework or coverage metrics mentioned.
Last push on 2026-06-27, 10 days before evaluation date, indicates active maintenance as of mid-2026. Project has been continuously maintained for 10 years since creation in 2016. Build status badge present but Travis CI link may be outdated. Community coordination via Zulip chat suggests ongoing developer engagement. No signals of abandonment, but pace of change appears measured rather than rapid.
ADOPT IF: You are a person with Type 1 diabetes seeking a customizable, open-source automated insulin delivery system, have technical competency to build and maintain the app, understand the regulatory and safety implications of using non-approved software, and value community transparency over commercial warranty. AVOID IF: You require FDA-approved therapy, lack Swift development skills, need professional vendor support, or prefer not to take personal responsibility for software reliability in a medical context. MONITOR IF: You are a health tech researcher or policy analyst interested in community-driven medical software, as this project illustrates both the potential and persistent challenges of decentralized healthcare innovation.
Independent dimensions
Mainstream potential
2/10
Technical importance
7/10
Adoption evidence
5/10
- Regulatory exposure: Project operates outside FDA approval framework. Users assume full liability. Legal status remains ambiguous in many jurisdictions.
- No professional support structure: Reliance on volunteer maintenance and community troubleshooting. No guaranteed response times or bug fixes.
- Medical device risks: Software failures could directly impact insulin delivery and blood glucose control. Lack of formal validation, redundancy, or failsafe mechanisms documented in README.
- User skill dependency: Installation, configuration, and troubleshooting require technical competency. Adoption limited by barrier to entry; potential for misuse by non-technical users.
- Sustainability uncertainty: Dependent on continued volunteer developer engagement. No commercial backing or funding model documented. Long-term maintenance not guaranteed.
Loop will likely remain a stable, niche-serving project sustained by a dedicated user community. Modest growth expected as Type 1 diabetes population grows and open-source healthcare awareness increases, but mainstream adoption is improbable given regulatory barriers and medical liability concerns. The project may evolve to integrate newer pump/CGM protocols or improve UI/UX, but fundamental mission and positioning will not change.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://loopdocs.org
- Language
- Swift
- License
- NOASSERTION
- Last updated
- 2w ago
- Created
- 123mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Live activity says open app to update widge
Omnipod dash critical pod fault within 1 and 9 hours before changing
Loop keeps crashing
Unable to change correction range
Feature Request: Show predicted glucose and bolus recommendation when no active pod is paired
Top contributors
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
LoopKit/Loop
this
|
1.7k | +7 | Swift | 7/10 | 2w ago |
 nightscout/AndroidAPS
|
1.1k | — | Kotlin | 8/10 | 19h ago |
 carekit-apple/CareKit
|
2.5k | — | Swift | 7/10 | 3mo ago |
 mrkai77/Loop
|
11.1k | — | Swift | 8/10 | 4d ago |
 Lakr233/BBackupp
|
2.6k | — | Swift | 6/10 | 2mo ago |
 KeyboardKit/KeyboardKit
|
1.8k | — | Swift | 7/10 | 1d ago |
Kotlin-based equivalent for Android. Similar community-driven, non-commercial positioning. Both serve users who self-build closed-loop systems. Loop is iOS-exclusive; AndroidAPS covers Android market. Neither directly competes with commercial CGM/pump manufacturers.
Apple's framework for health app development, has higher star count (2,522). CareKit is a general-purpose health app platform; Loop is a specialized application. Different scope and purpose; CareKit is infrastructure, Loop is a finished product for a specific use case.
Loop operates outside the commercial/regulatory framework. Lacks FDA approval but offers user autonomy and customization. Appeals to users who want open-source control or lack access to approved options. Not a direct replacement but fills a different role in the diabetes technology landscape.
Complementary project for glucose data sharing and remote monitoring. Loop and Nightscout are often used together. Not competitors but members of the same ecosystem.
