Steve Jobs introduced the iPad on January 27, 2010. The reviews were mixed. "Just a big iPhone." "A laptop for people who don't need a laptop." John Gruber called it "the most important product Apple has ever introduced." Walt Mossberg called it "a cusp between two worlds."
We bought one the day it launched, passed it around the office, and spent the afternoon arguing about what it was for.
By November we had our first enterprise app shipping on it. By 2012 we understood that the iPad had defined a new class of user interface that didn't come from phones or desktops - it came from paper.
The First Client: Field Inspectors
A construction company approached us in July 2010. Their field inspectors used clipboards. Paper forms, 47 fields per inspection, handwritten notes, photographs taken on a separate camera, all of it assembled at the office into a PDF report that took 2-3 hours to compile per site.
They'd tried building a mobile app on Windows Mobile. Users hated it. The screen was too small to navigate the form comfortably. Stylus input was error-prone. They'd given up.
The iPad changed the calculation. A screen large enough to show an entire form section without scrolling. No stylus - touch with gloved fingers was viable. The A4X chip was fast enough to handle large form rendering without lag.
The first design question: should we replicate the paper form on screen?
We did, initially. Tab-ordered fields, labels aligned to the left, data entry on the right. A faithful digital recreation of the paper clipboard.
The inspectors didn't like it. "It looks like a website." They were right - we'd designed it for a mouse cursor on a 1280×1024 monitor, not for thumbs on a 1024×768 touchscreen.
Rethinking Touch Targets
Apple's Human Interface Guidelines specified minimum touch targets of 44×44 points. On the iPad's 132 PPI display at the time, that was 44 physical pixels - about 8.3mm square. Enough to tap with a fingertip, not with a gloved construction worker's thumb.
We went to 60×60 minimum. Form fields became tall enough to tap without zooming in. Buttons became unmistakably button-shaped:
// Creating a properly sized touch target in Objective-C
UIButton *approvalButton = [UIButton buttonWithType:UIButtonTypeCustom];
approvalButton.frame = CGRectMake(0, 0, 200, 60); // 60pt height minimum
approvalButton.titleLabel.font = [UIFont boldSystemFontOfSize:20];
// Visual feedback for touch - important for field workers
[approvalButton setBackgroundImage:[self imageWithColor:[UIColor greenColor]]
forState:UIControlStateNormal];
[approvalButton setBackgroundImage:[self imageWithColor:[UIColor darkGreenColor]]
forState:UIControlStateHighlighted];
// The highlighted state needs to be visually distinct - a gloved finger
// can't feel whether they've touched the button
The highlighting state - the visual feedback when a button was pressed - was more important on the iPad than anywhere else. Desktop users had hover states and cursor changes. Mobile phone users tapped buttons with bare fingertips. Field workers tapped with leather gloves, tool-calloused fingers, and winter hands. The visual state change had to be obvious.
The Master-Detail Pattern
The iPad's large screen introduced a navigation pattern that didn't exist on phones: master-detail. A persistent sidebar showing the list, a main area showing the detail. Apple's Mail app used it. We used it for the inspection forms:
// UISplitViewController - the core of iPad master-detail
UISplitViewController *splitVC = [[UISplitViewController alloc] init];
// Left: list of form sections (20% width)
FormSectionListViewController *masterVC = [[FormSectionListViewController alloc] init];
// Right: current section's fields (80% width)
FormDetailViewController *detailVC = [[FormDetailViewController alloc] init];
splitVC.viewControllers = @[masterVC, detailVC];
splitVC.delegate = detailVC;
// In portrait mode, the master disappears - show as popover
- (void)splitViewController:(UISplitViewController *)svc
willHideViewController:(UIViewController *)aViewController
withBarButtonItem:(UIBarButtonItem *)barButtonItem
forPopoverController:(UIPopoverController *)pc {
barButtonItem.title = @"Sections";
self.navigationItem.leftBarButtonItem = barButtonItem;
self.masterPopoverController = pc;
}
This single UX pattern - persistent navigation list beside the content - made the iPad feel like a completely different product from the iPhone. You didn't go back. You selected. The mental model was a binder with tabs, not a linear stack of screens.
Photography Integration
Paper-based inspections required attaching photographs. The inspector would photograph defects, print them, staple them to the report. Our app embedded photos directly in the form:
- (void)takePhoto:(UIButton *)sender {
// Tag button with the field index so we know which form field gets the photo
NSInteger fieldIndex = sender.tag;
UIImagePickerController *picker = [[UIImagePickerController alloc] init];
picker.sourceType = UIImagePickerControllerSourceTypeCamera;
picker.delegate = self;
// Store for use in delegate callback
self.currentPhotoFieldIndex = fieldIndex;
// On iPad, UIImagePickerController must be in a popover
// (presenting fullscreen crashes on iPad in 2010-2012)
UIPopoverController *popover = [[UIPopoverController alloc] initWithContentViewController:picker];
[popover presentPopoverFromRect:sender.frame
inView:self.view
permittedArrowDirections:UIPopoverArrowDirectionAny
animated:YES];
self.cameraPopover = popover;
}
- (void)imagePickerController:(UIImagePickerController *)picker
didFinishPickingMediaWithInfo:(NSDictionary *)info {
UIImage *photo = info[UIImagePickerControllerOriginalImage];
// Scale down immediately - 8MP photos at full res would fill memory fast
UIImage *scaled = [self scaleImage:photo toMaxDimension:1024];
// Store with field reference
self.formPhotos[@(self.currentPhotoFieldIndex)] = scaled;
// Show thumbnail in form
[self updatePhotoThumbnail:scaled atIndex:self.currentPhotoFieldIndex];
[self.cameraPopover dismissPopoverAnimated:YES];
}
The photo attachment feature alone cut report compilation time from 2-3 hours to 15 minutes. Not because the form was faster to fill out - field inspectors were equally fast on paper. Because the assembly was instant: photos were in the form, not on a separate device that needed importing.
Offline-First Before It Had a Name
Construction sites don't have reliable WiFi. Cellular coverage in partially-built buildings is unpredictable. The app had to work without a network connection.
We used SQLite on-device (via Core Data) as the primary store. Network sync was secondary:
// Offline-first data strategy
@implementation InspectionStore
- (Inspection *)createInspection {
Inspection *inspection = [NSEntityDescription
insertNewObjectForEntityForName:@"Inspection"
inManagedObjectContext:self.localContext];
inspection.localID = [[NSUUID UUID] UUIDString];
inspection.syncStatus = @"pending"; // Needs upload
inspection.createdAt = [NSDate date];
[self.localContext save:nil];
return inspection;
}
- (void)syncPendingInspections {
// Only called when network is available
NSFetchRequest *request = [NSFetchRequest fetchRequestWithEntityName:@"Inspection"];
request.predicate = [NSPredicate predicateWithFormat:@"syncStatus == 'pending'"];
NSArray *pending = [self.localContext executeFetchRequest:request error:nil];
for (Inspection *inspection in pending) {
[self uploadInspection:inspection completion:^(BOOL success, NSString *serverID) {
if (success) {
inspection.serverID = serverID;
inspection.syncStatus = @"synced";
[self.localContext save:nil];
}
}];
}
}
@end
We checked network reachability on app foreground and synced then. Inspectors filled out forms all day in areas with no signal, and data uploaded when they returned to the office WiFi. No data loss, no blocking on network availability.
What the iPad Changed Permanently
Five years after we shipped that first inspection app, field workers across the construction industry were using iPads. The clipboard died. Paper forms became legacy systems that needed "digitization projects." The 2-3 hour report assembly task vanished.
The design lessons became standard iPad UX practice:
- Master-detail for navigation-heavy content
- 60px+ touch targets in field environments
- Offline-first with sync - never assume connectivity
- Direct manipulation (drag-and-drop, pinch-to-zoom) over menu-driven actions
- Photography as a first-class form input
The iPad didn't replace the laptop. It didn't replace the phone. It replaced the clipboard, the printed manual, the paper form. Jobs called it "the most intimate relationship with technology" - closer than a laptop, more capable than a phone. For field workers holding it at chest height, walking through a construction site, that description was literally accurate.
Aunimeda develops mobile applications for iOS and Android - from MVP to production-ready apps with full backend integration.
Contact us to discuss your mobile project. See also: Mobile App Development, Mobile Game Development