3 ms·
Those aren't the only two options. The better one IMO is large teams with small sub-groups, each with at least one person who knows the whole stack top to botto
by freehunter 8y ago
Those aren't the only two options. The better one IMO is large teams with small sub-groups, each with at least one person who knows the whole stack top to bottom, with frequent communication between the subgroups. That's pretty typical in the corporate world where each manager has multiple teams under them, one architect, and a liaison to an advisory board to communicate to other teams.
The reason I prefer this approach is something Apple seems to be struggling with: lots of small teams breed lots of small solutions that don't add up to one big solution.
Case in point: I have a latest-gen iPhone and iPad. The iPhone has a touch-sensitive home button, while the iPad has a real actual click-button. The iPhone has no headphone jack, the iPad does. The iPhone is waterproof, the iPad is not. The iPhone has stereo speakers in landscape, the iPad does not. The iPhone has force touch, the iPad does not. The cheapest iPad has support for the Pencil, the most expensive iPhone does not. Moving on to the Macbook, the iPhones and iPads use Lightning to charge, while the Macbooks use USB-C and have never in their history ever even included a Lightning port. The Pencil exclusively uses Lightning to charge and has no other way of connecting, and even helpfully includes a Lighting-to-Lightning adapter in the box, still rendering it completely incapable of charging from a Macbook without yet another adapter to convert Lightning (male) to Lightning (female) to USB-C (male).
There's no real reason for these differences except to say the teams don't work together to synchronize their engineering efforts. Individually each one is a great engineering achievement. Combined, it's a mess of small solutions that don't add up to one big solution.
- Terretta 8y agoAlternative explanation to incompetence: iPhone, iPad, and MacBooks are different form factors for different use cases. iPhone is used in more active situations. Not running in rain with iPad strapped to arm. On iPhone stereo speakers in landscape, not sure what that one means; for me it’s the iPad with speakers on both sides while in landscape. Force touch requires force, easy with a phone in your hand, less easy if iPad propped on origami Smart Keyboard. (Could be reason for button diffs too, light touch with haptics vs. real touch, or just a very common use of home button on iPad is while landscape so you squeeze a “real” button between your thumb and forefinger.) The phone is not slate sized, why should it try to be a slate? Don’t know why you’d be charging a pencil from a MacBook some way you couldn’t charge an iPad with. To me, seem to be plausible reasons for every one of these differences beyond just “teams don’t work together”. Certainly both are possible, just saying the device modalities are different. ATV, HomePod and Watch UIs are different too.
- freehunter 8y agoPeople read on iPads by the pool or lake or on a boat all the time. There's a good reason to make it waterproof. Re: the stereo speakers. The iPhone uses the earpiece as one speaker and the bottom speakers as another, so when it's on its side and you're watching Netflix, sound comes out of the top and bottom. The iPad (except for the iPad Pro) only has speakers on the bottom, so when you're using the Smart Cover and watching Netflix, all the sound comes out the bottom. On a device far larger than the iPhone, this really makes a difference. I don't think a device needs to be a slate in order to be worth writing on. Scribbling notes is easier on an iPhone since you can hold it in your hand, and since you have unlimited pages the increased size of the iPad doesn't matter.