> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nativeline.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Building for iPhone, iPad, and Mac
> Platform-specific guidance for building on all Apple platforms
Nativeline supports three platforms: **iPhone**, **iPad**, and **Mac**. You choose your platform when creating a new project on the home page, and that choice shapes everything — the UI patterns the AI uses, how your app is tested, and how you distribute it.
## Choosing Your Platform
Each platform has its own strengths. Pick the one that best fits what you're building.
Standard mobile apps. The most common choice. Full iOS feature set with compact, touch-first UI.
Larger canvas with room for sidebars, split views, and richer layouts. Great for productivity and content apps.
Desktop apps with menu bars, keyboard shortcuts, and window management. Native macOS experience.
## iPhone Apps
iPhone apps use standard mobile UI patterns that feel familiar to every iOS user.
**What you get:**
* Tab bars for top-level navigation
* Navigation stacks for drill-down flows
* Lists, forms, and detail views
* Full access to iOS APIs (camera, location, notifications, etc.)
**Testing:** Your app runs in an embedded iPhone simulator right inside Nativeline.
**Distribution:** Publish via TestFlight for beta testing, or submit to the App Store.
**Example prompts:**
```
Create a fitness tracker with daily workout logging and progress charts
```
```
Build a habit tracking app with streaks and daily reminders
```
```
Make a recipe organizer where I can save recipes and generate shopping lists
```
## iPad Apps
iPad apps take advantage of the larger screen to show more content and use richer navigation patterns.
**What you get:**
* Sidebar navigation using `NavigationSplitView`
* Split views for master-detail layouts
* More room for data-dense interfaces
* Support for Apple Pencil interactions
* Full access to iPadOS APIs
**Testing:** Your app runs in an embedded iPad simulator inside Nativeline.
**Distribution:** Publish via TestFlight for beta testing, or submit to the App Store.
**Example prompts:**
```
Create a recipe manager with a sidebar for categories and a detail view for each recipe
```
```
Build a PDF annotator where I can highlight text and add notes
```
```
Make a drawing canvas app with layers and brush customization
```
## Mac Apps
Mac apps are native macOS applications with proper desktop UI conventions. No Catalyst, no iOS port — these are real Mac apps.
**What you get:**
* Menu bar support with custom menus
* Keyboard shortcuts and keyboard navigation
* Window management (resizing, multiple windows)
* Native macOS controls and layout patterns
* Toolbar support
**Testing:** Mac apps run natively in a window on your Mac — no simulator needed.
**Distribution:** Three options:
* **TestFlight** for beta testing
* **App Store** for public distribution
* **DMG export** for distribution outside the App Store
**Example prompts:**
```
Create a clipboard manager that lives in the menu bar
```
```
Build a markdown editor with live preview and file management
```
```
Make a window manager that lets me snap windows to screen regions with keyboard shortcuts
```
## Platform Comparison
| | iPhone | iPad | Mac |
| ---------------- | ---------------------- | ---------------------- | ---------------------------- |
| **Screen size** | Compact | Regular | Full desktop |
| **Navigation** | Tab bar, stack | Sidebar, split view | Menu bar, toolbar |
| **Input** | Touch | Touch + Pencil | Mouse + keyboard |
| **Testing** | Embedded simulator | Embedded simulator | Runs natively |
| **Distribution** | TestFlight / App Store | TestFlight / App Store | TestFlight / App Store / DMG |
## Tips for Each Platform
* Keep your UI simple and focused — screen space is limited
* Use tab bars for 3-5 top-level sections
* Think about one-handed use — put key actions within thumb reach
* Test with different Dynamic Type sizes to make sure text scales well
* Use sheets and modals sparingly to avoid navigation confusion
* Take advantage of sidebars — they're the standard iPad navigation pattern
* Don't just scale up an iPhone layout. Use the extra space for split views and richer content
* Consider landscape and portrait orientations — iPad users rotate frequently
* Multi-column layouts work well for list-detail flows
* Use popovers instead of full-screen modals when possible
* Add keyboard shortcuts for common actions — Mac users expect them
* Use the menu bar for navigation and commands, not just toolbar buttons
* Support window resizing gracefully — your layout should adapt to different window sizes
* Consider adding a menu bar extra (status bar icon) for utility apps
* Respect macOS conventions: Cmd+Q to quit, Cmd+W to close window, Cmd+, for preferences
You can't change a project's platform after creation. If you want to build for a different platform, create a new project.
## Which Platform Should You Pick?
If you're not sure, ask yourself:
* **"Will people use this on the go?"** — Build for iPhone.
* **"Does this need a big canvas or complex navigation?"** — Build for iPad.
* **"Is this a productivity tool or utility people use at their desk?"** — Build for Mac.
You can always create separate projects for different platforms if your app idea works across multiple form factors.
***
Start a new project and choose your platform.
Test your iPhone and iPad apps without leaving Nativeline.