ios-26-platform
Skill0 starsChanged 2 months agoMITView on GitHub
Use when implementing iOS 26 features (Liquid Glass, new SwiftUI APIs, WebView, Chart3D), deploying iOS 26+ apps, or supporting backward compatibility with iOS 17/18.
In this repository21 other files it gives its agents.
- animateSkill
- composable-architectureSkill
- find-animation-opportunitiesSkill
- generating-swift-package-docsSkill
- hapticsSkill
- improve-animationsSkill
- ios-higSkill
- ios-simulator-skillSkill
- localizationSkill
- review-animationsSkill
- spm-build-analysisSkill
- storekitSkill
- swift-concurrencySkill
- swift-dataSkill
- swift-diagnosticsSkill
- swift-networkingSkill
- swift-styleSkill
- swift-testingSkill
- swiftuiSkill
- write-swiftSkill
- xcode-buildSkill
The file
Files
iOS 26 Platform
iOS 26 introduces Liquid Glass, Apple's next-generation material design system that dynamically bends light, moves organically, and adapts automatically across all platforms.
Overview
iOS 26 modernizes UI with new materials (Liquid Glass), SwiftUI APIs (WebView, Chart3D, @Animatable), and advanced features (@BackoffAnimation, free-form windows). The core principle: modern UI gets updated automatically at compile time; most Liquid Glass benefits are "free" from recompiling with Xcode 26.
Reference Loading Guide
ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.
| Reference | Load When |
| Liquid Glass | Implementing glass effects, choosing Regular vs Clear variants, or understanding visual properties |
| Automatic Adoption | Understanding what iOS 26 changes automatically vs what requires code |
| SwiftUI APIs | Using WebView, Chart3D, @Animatable, AttributedString, or new view modifiers |
| Toolbar & Navigation | Customizing toolbars with spacers, morphing, glass button styles, or search |
| Backward Compatibility | Supporting iOS 17/18 alongside iOS 26, or using UIDesignRequiresCompatibility |
Core Workflow
- Check deployment target — iOS 26+ required for Liquid Glass
- Recompile with Xcode 26 — Standard controls get glass automatically
- Identify navigation layer — Apply glass to tab bars, toolbars, navigation (not content)
- Choose variant — Regular (95% of cases) or Clear (media-rich backgrounds only)
- Add @available guards — For backward compatibility with iOS 17/18
- Test accessibility — Verify Reduce Transparency, Increase Contrast, Reduce Motion
Common Mistakes
- Ignoring backward compatibility — Targeting iOS 26+ without
@availableguards breaks iOS 17/18 support. Always useif #available(iOS 26, *)for Liquid Glass or new APIs. - Over-using glass effect — Applying glass to content areas, not just navigation, creates visual noise. Glass works for: tab bars, toolbars, sheets, navigation. NOT for content areas.
- Animation performance issues — Liquid Glass animations can be expensive. Respect Reduce Motion accessibility setting and profile with Instruments 26 before shipping.
- Assuming Clear variant looks good — Clear is for media-rich backgrounds only (photos, video). Regular variant is correct 95% of the time. Only use Clear if you explicitly need the ultra-transparency.
- Not testing on actual devices — Simulator rendering differs from hardware. Test glass effects on iPhone 15 Pro, iPad, and Mac to verify visual quality.
- Using old UIView patterns with new glass — Mixing UIView-based navigation with iOS 26 glass creates inconsistent appearances. Migrate fully to SwiftUI or wrap carefully with UIViewRepresentable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

