The value of a reference design is basically zero without the schematics/layout and BSP. Or do you just mean upstreaming BSP drivers?
The interesting part is the choice of components, the rationale behind that choice, and the software support.
I suppose that Google makes available the Android OS with support for all the new capabilities as they emerge (OLED, NFC, fingerprint scanners, etc) which OEMs can leverage with their hardware and closed-source software (both apps and drivers).
The Pixel line is the Google's vision of the platform, with Google's control over hardware implementation and a commitment to support it (longer than many OEMs but not nearly as great as iPhones).
Root comment author here: I used the term mostly in mockery of the hobby-level effort Google has put into Pixel in the past. However, when it cones to Android devices the lines are blurred between "reference design" and "competitor flagship".
Consider:
* Android's roadmap is controlled by Google, which decides which features go into the next release. Once those features are in the codebase, they can be used by any OEM
* OHA OEMs get early access to upcoming Android versions and work with Google
* Android devices share the same set of suppliers for sensors/chips/SoC/modems: this is highly commoditized. Once the API & drivers for a feature are there, any OEM will have an easier time implementing it; perhaps choosing a different part number in the same product line.
So Google in not sharing its circuit diagrams & CAD files, but the OEMs don't have to reverse-engineer anything post-release either. The reality is someplace inbetween: cooperative development
This is mostly hypothetical - does Samsung actually do that in practice? I haven't heard of anyone using -, nor am I aware of Samsung publicizing any such unifying services.
I own several Samsung devices, and have a Samsung account, and it is something of an annoyance to use. The power/potential is there no doubt, but services aren't a Samsung core competency.
I understand why one would bucket Pixel hardware into that old played out “reference hardware”. That has been Google’s approach over the years.
But herein lies my point: Google has changed their tune. The top brass have now bought into the integration of hw, sw and services ecosystem that Apple had set out with from the get go. This isn’t some Googler asking Sundar for budget so they can make some vanilla smartphone. This is Sundar putting a stake in the ground with real long term budget to saying: 10 years from now, if we continue to execute on pixel, the US market and perhaps more will be a healthier mix of Apple and Google phones. And I think a reasonable target is like 2:1 iphone to Pixel.
Given the importance of the phone as the primary computing device in peoples lives and the amount of profit Google draws in from consumer computing activity, and the lack of leverage Google really has over other OEMs phones, it is super important for Google to eventually hit something like 2 iphones to 1 pixel in sales. Its no a long shot either. With enough money and time this will happen.
I'm not convinced that Pixel hardware is anything other than reference designs: each device is developed from a clean slate and none sell in appreciable numbers
> Samsung phones are about the Samsung ecosystem.
What Samsung ecosystem? Samsung makes fantastic stand-alone hardware, but it's no ecosystem. No one buys Samsung earbuds because they work particularly well with the Galaxy 22, or their calendar and music are already integrated with Bixby