I constantly see those projects that would benefit from a screenshot in a readme, but for some reason the thought about adding one doesn't even come to the authors' mind, even though it's pretty obvious. I'd really like to know what's going on.
If you look at the history they have been working on this for a few months. The announcement probably was tied to this public release being cut for testing.
With a seemingly insurmountable workload - maintain an actually secure OS fork - for a small team, I wonder how GrapheneOS prioritizes things like messaging apps? I'm not saying it's wrong at all; I am just interested in the thinking inside a project like that.
I can imagine many reasons to devote resources to it:
* A platform is only as good as its apps. If they want to grow GOS in the general public, it requires a good SMS/MMS messaging app.
* LLM tools greatly reduce development costs, especially for well-known functions like text messaging.
* Without secure messaging (as far as SMS/MMS can be secure), the platform security is greatly reduced.
* GOS got a big donation, or has a volunteer that wants to do messaging ...
But idk what I'm talking about. What is their approach?
Well they're going to be shipping GOS on Motorola and I think some other devices, so basic things like the messaging app need to actually have some polish to them. I really like GrapheneOS overall as-is, but the messaging app felt like baby's first texting app. Not necessarily their fault since it's pretty much straight out of AOSP if I understand correctly. But any time I've installed GrapheneOS, the messaging app is one of two things I must replace every time (the other being the downright bad AOSP keyboard).
If they fix(ed) their messaging app and their keyboard, then they've really eliminated a lot of potential complaints if a less tech-savvy crowd ends up buying future Motorolas.
Looks prettier but a shame an obvious regression happened for one of my primary use-cases: copying one-time codes. Long pressing on a link selects the entire SMS instead of bringing up a menu for the link. [0]
Makes me wonder about all the testing now
And the issue worded/tagged as a feature instead of a regression. Are the devs aware the feature existed before?
Now, can we please get the long-awaited full system backup feature? We pay you for a reason!
(sarcasm obvious, but indeed full system backup is sorely missing. Seedvault is crap, not an option)
How about some screenshots?
I constantly see those projects that would benefit from a screenshot in a readme, but for some reason the thought about adding one doesn't even come to the authors' mind, even though it's pretty obvious. I'd really like to know what's going on.
Does anyone know if this is something that we can install now, or if it will show up in the next OS release?
You can go to the GOS App Store, choose the Messaging app, click 3 dots at the top and choose the Alpha release channel to get it now
They mentioned you can use the Alpha from their app installer.
Good to know! For others: You open their app store, go into messaging, hamburger menu, select release channel, and choose alpha.
[delayed]
Does it do RCS?
No. RCS is still quite hard to actually implement. There's an open issue for it but the effort is mildly herculean.
AFAIUI though GOS does intend on providing an RCS impl eventually even if it takes years to do.
That was really fast, they only announced it like a day or two ago IIRC? Also: no screenshots of the redesigned interface?!
If you look at the history they have been working on this for a few months. The announcement probably was tied to this public release being cut for testing.
With a seemingly insurmountable workload - maintain an actually secure OS fork - for a small team, I wonder how GrapheneOS prioritizes things like messaging apps? I'm not saying it's wrong at all; I am just interested in the thinking inside a project like that.
I can imagine many reasons to devote resources to it:
* A platform is only as good as its apps. If they want to grow GOS in the general public, it requires a good SMS/MMS messaging app.
* LLM tools greatly reduce development costs, especially for well-known functions like text messaging.
* Without secure messaging (as far as SMS/MMS can be secure), the platform security is greatly reduced.
* GOS got a big donation, or has a volunteer that wants to do messaging ...
But idk what I'm talking about. What is their approach?
Well they're going to be shipping GOS on Motorola and I think some other devices, so basic things like the messaging app need to actually have some polish to them. I really like GrapheneOS overall as-is, but the messaging app felt like baby's first texting app. Not necessarily their fault since it's pretty much straight out of AOSP if I understand correctly. But any time I've installed GrapheneOS, the messaging app is one of two things I must replace every time (the other being the downright bad AOSP keyboard).
If they fix(ed) their messaging app and their keyboard, then they've really eliminated a lot of potential complaints if a less tech-savvy crowd ends up buying future Motorolas.
Looks prettier but a shame an obvious regression happened for one of my primary use-cases: copying one-time codes. Long pressing on a link selects the entire SMS instead of bringing up a menu for the link. [0]
Makes me wonder about all the testing now
And the issue worded/tagged as a feature instead of a regression. Are the devs aware the feature existed before?
[0] https://github.com/GrapheneOS/Messaging/issues/292
I am disappointed how bloaty this app is because it uses electron
I do not see Electron anywhere? It looks like a native Android app that uses Jetpack Compose.