Any hardware development coming with components that enable GrapheneOS is a big win. We just need more of it, ideally at least a few more device lines that GrapheneOS can structurally support.
Only having one hardware line is a problem, just as it was with the Pixel line. If that one vendor changes something important, like dropping ARM Memory Tagging Extension (MTE) like Pixel did w/ 11s, boom, you're potentially screwed.
Having a single line of phones that an OS depends on is a perilous position to be in. How many different device lines the GrapheneOS team can realistically support at the same time, I don't know.
Long term, the ideal might actually be GrapheneOS developing its own phones, maybe releasing 1-2 models every couple of years: one mid-range device and one flagship with higher margins that could contribute more meaningfully to development. Pick whatever hardware makes the most sense, and ideally design the two around the same architecture so improvements and porting are easier between them.
That would require a shit ton of resources, though, and I'm not sure they can achieve that from their current market position.
Any hardware development coming with components that enable GrapheneOS is a big win. We just need more of it, ideally at least a few more device lines that GrapheneOS can structurally support.
Only having one hardware line is a problem, just as it was with the Pixel line. If that one vendor changes something important, like dropping ARM Memory Tagging Extension (MTE) like Pixel did w/ 11s, boom, you're potentially screwed.
Having a single line of phones that an OS depends on is a perilous position to be in. How many different device lines the GrapheneOS team can realistically support at the same time, I don't know.
Long term, the ideal might actually be GrapheneOS developing its own phones, maybe releasing 1-2 models every couple of years: one mid-range device and one flagship with higher margins that could contribute more meaningfully to development. Pick whatever hardware makes the most sense, and ideally design the two around the same architecture so improvements and porting are easier between them.
That would require a shit ton of resources, though, and I'm not sure they can achieve that from their current market position.