The open-source AID system for Android — same oref1 algorithm as Trio, widest pump compatibility of any DIY system, remote bolusing for caregivers, and smartwatch integration. The iOS-free path to advanced DIY closed-loop therapy.
Device specifications change frequently — always verify current information directly with the manufacturer before making any decisions. Full disclaimer.
Curious about AndroidAPS? Start here.
AndroidAPS is not FDA-cleared and is not a commercial product. It is open-source software built and maintained by volunteer community members. You build it yourself, you run it at your own risk, and you are responsible for its safe use. The AAPS documentation itself describes it as "carrying out a medical experiment on yourself." Read the full documentation at androidaps.readthedocs.io before starting.
Critical safety note: Do NOT use AndroidAPS if you take SGLT-2 inhibitors (gliflozins — e.g., Farxiga, Jardiance, Invokana). SGLT-2 inhibitors lower blood glucose independently. Combined with an algorithm that reduces basal in response, the risk of DKA from under-insulinization is significantly elevated. This contraindication is absolute.
AndroidAPS (AAPS) runs the same oref1 algorithm as Trio — the advanced open-source AID algorithm developed from OpenAPS, featuring Super Micro Boluses, Unannounced Meal detection, Dynamic ISF, and Autosens. The key difference from Trio: AAPS runs on Android smartphones, not iPhone. And it supports a significantly wider range of insulin pumps — including DANA pumps, Accuchek Combo, and others not available on iOS-based systems. For Android users, or users with pumps that Loop/Trio don't support, AAPS is often the only viable DIY path.
AAPS supports Omnipod EROS/Dash, older Medtronic pumps, DANA RS/i, Accuchek Combo, Eopatch, Medtrum, Equil, and others. No other DIY system — and certainly no commercial system — works with this range of hardware. If your pump isn't supported by Loop or Trio, AAPS may support it.
Parents and caregivers can remotely deliver boluses using the AAPSClient app — not just view data. This is a significant capability for pediatric patients: a parent can issue a correction or meal bolus from their own phone without touching the child's device. No commercial system offers this.
AAPS supports multiple smartwatch platforms for displaying glucose, IOB, and loop status — and some watches support bolusing directly from the wrist. Wear OS watches offer the most complete integration. For discreet monitoring without pulling out a phone, this is unmatched.
AAPS includes a built-in automation engine — you can create triggers and actions for nearly any scenario: time of day, BG level, activity detection, location, or connection status. Exercise automations, circadian insulin adjustments, and snooze functions are all possible without manual intervention.
AAPS users tend to be technically sophisticated — they compiled the app themselves, learned Android Studio, and configured oref1 settings. Their understanding of insulin pharmacokinetics is often advanced. Listen to their reporting.
Critical: SGLT-2 inhibitors are absolutely contraindicated with AAPS. Screen for gliflozin use at every visit. The combination elevates DKA risk substantially due to reduced insulin delivery.
Most AAPS users upload to Nightscout. Ask for their Nightscout URL or Tidepool access. You'll see CGM data, SMB deliveries, autosens ratios, and algorithm decisions — often richer data than commercial platforms.
Same as Trio: duration of insulin action is 10 hours in oref1. This is intentional and load-bearing in the algorithm's IOB model. Do not advise patients to change it to the 4–6 hours typical of commercial systems.
One of AndroidAPS's most distinctive features is its structured Objectives system — a mandatory learning progression that unlocks algorithm features in stages, requiring you to demonstrate understanding before accessing each capability. You cannot skip objectives. This is a safety design, not an inconvenience.
Configure AAPS, connect pump and CGM, set reporting server, configure safety limits, review profile settings. You're not looping yet — you're verifying everything is connected correctly.
AAPS makes basal rate suggestions but does not act automatically. You review each recommendation and apply it manually. The goal: understand why the algorithm wants to do what it's suggesting before it can do it on its own.
AAPS can now act automatically, but only to suspend or reduce insulin to prevent lows. No automatic increases yet. Run for at least 5 days. This builds trust in the safety layer before the full algorithm activates.
Full closed loop with basal adjustment, but maximum IOB is set to zero — no automatic boluses. The system can reduce or suspend insulin but cannot add any above your programmed basal.
Before unlocking SMBs, you must demonstrate 3 days of stable management and review your basal rates, ISF, and I:C ratio. The algorithm checks your settings are plausible. This is where most users spend meaningful time optimizing.
Normal Temp Target use, full SMB capability, autosens enabled. The algorithm is now operating with the same feature set as Trio. Advanced features like Dynamic ISF and UAM can now be configured. Regular time to complete: 2–4 weeks total from Objective 1.
Patient uses Android phone. Patient has a pump not supported by Loop/Trio (DANA, Accuchek). Patient needs remote bolusing for caregiver (AAPSClient). Patient wants smartwatch integration. International patient with locally available pumps that aren't FDA-focused.
Patient uses iPhone. Patient uses Omnipod Dash (works on both, but Trio is more accessible). Patient prefers browser-based build process. Patient is less technically experienced — Trio's setup is generally easier than AAPS's Android Studio build process.
Both run oref1 (OpenAPS). Both have SMBs, UAM, Dynamic ISF, Autosens, DIA locked at 10 hours. Clinical outcomes are comparable between the two systems when settings are well-calibrated. The difference is platform, pump support, and build process.
Both AAPS and Trio: absolutely contraindicated with SGLT-2 inhibitors. Screen at every visit. If a patient is added to gliflozins while on AAPS, the DIY loop must be discontinued or the medication changed.
oref1 (OpenAPS) — same as Trio. SMBs, UAM, Dynamic ISF, Autosens, DIA locked at 10 hours. Structured Objectives unlock features progressively. Full closed loop experimental mode available.
Android phone required (not iOS). Broadest pump support of any DIY system — Omnipod Dash, DANA, Accuchek, older Medtronic, others. CGM: Dexcom natively, xDrip+ for expanded sensor support.
AAPSClient app: caregivers can remotely bolus, set targets, change profiles. No commercial system offers equivalent caregiver bolusing. Requires Nightscout for data relay. Smartwatch integration for wrist-based monitoring and bolusing.
Absolute: Do not use with SGLT-2 inhibitors (gliflozins). DKA risk elevated. Screen for gliflozin use at every visit.
Pancreas4ALL (Diabetes Technol Ther 2023, prospective RCT). OPEN project (EU-funded, outcomes data). Pediatric retrospective (Pediatr Diabetes 2021). Growing body consistent with commercial AID evidence.
Nightscout (primary — required for AAPSClient). Tidepool (alternative). Both provide AGP-style reporting for clinic review. Nightscout also enables caregiver remote view and AAPSClient command relay.