Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS' rewritten Messages app is released

github.com

Post reply on HN
Print view View original

51–60 of 258 posts

Re: GrapheneOS' rewritten Messages app is released

#51

Post by em-bee »

gremlinunderway wrote: post #38
gbalduzzi wrote: post #22

Earlier quoted context omitted.

I think in many cases the authors value functionality much more then esthetics. Which is a bummer because it is a complete different point of view from the more typical user experience

Yeah but see, we're talking about a functionality that is inherently visual. Ergonomics has nothing to do with esthetics, and it's such a dumb excuse to hand wave aside interface issues as of they are just about "making things look pretty"

exactly, i am looking at screenshots for apps to get an idea about their functionality.

Re: GrapheneOS' rewritten Messages app is released

#52

Post by subscribed »

mrd3v0 wrote: post #46

I wish they prioritised the call app. It is beyond appalling. You can't even determine when a call happened, beyond the generic low fidelity "[time] ago". It also almost feels like tapping anything makes me accidentally call people. Abhorrent UI/UX to be completely honest.

What? :)

You mean the perfectly functional (if barebones) AOSP call app? :)

Re: GrapheneOS' rewritten Messages app is released

#55

Post by okanat »

mrd3v0 wrote: post #46

I wish they prioritised the call app. It is beyond appalling. You can't even determine when a call happened, beyond the generic low fidelity "[time] ago". It also almost feels like tapping anything makes me accidentally call people. Abhorrent UI/UX to be completely honest.

I'm using LineageOS so I have the AOSP Phone app. If Graphene uses the same, then you can actually determine the exact time of call, but you need to jump through a couple of hoops: Go to "Call History" from the three dots then click on the call of interest. You'll see a button called "Call Details". Then you can see the exact time.

Re: GrapheneOS' rewritten Messages app is released

#56

Post by tcfhgj »

OneDeuxTriSeiGo wrote: post #7
mewse-hn wrote: post #4

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.

also I think RCS is way to insecure for Graphene OS - they have no way of making sure the communication is actually 100% secure.

In my experience, Graphene OS doesn't make compromises.

Re: GrapheneOS' rewritten Messages app is released

#57

Post by subscribed »

microtonal wrote: post #28
mmooss wrote: post #5

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…

A bunch of the AOSP apps feel like you have to rewrite them for modern standards now and then you can basically have them in maintenance mode for years. The AOSP messaging app has also lasted for 15+ (?) years and has basically had no maintenance from Google for many years. Modernizing these apps seems very high-impact. These are the very first things a new user sees and after the initial modernization, they should b…

> Messaging, high impact.

Messaging can be replaced with one of the hundreds decent messaging apps.

Unlike the backup app which is utterly unusable, untrustworthy and frankly crap. And CANNOT be replaced by anything else.

As it stands it's impossible to have reliable backups in GOS.

Re: GrapheneOS' rewritten Messages app is released

#58

Post by em-bee »

bramhaag wrote: post #47
tcoff91 wrote: post #45

Earlier quoted context omitted.

For those of us out of the loop, could someone summarize the situation?

> Fairphone has said they don't plan to add a secure element. It can be seen from their current devices that they don't fully keep up with privacy/security backports and lag a year behind on shipping yearly OS releases. They skip over the monthly and quarterly releases entirely. They replaced their own non-GMS Fairphone OS with a dramatically less secure /e/OS option in partnership with Murena. They clearly demonstra…

They replaced their own non-GMS Fairphone OS with a dramatically less secure /e/OS

it sounds like they are saying that /e/OS is less secure than fairphone's own OS. with all criticism against /e/OS taken into account, i highly doubt that fairphone would have been able to make their own version of android more secure than /e/OS when they are not even interested in working on that.

Re: GrapheneOS' rewritten Messages app is released

#59

Post by Telaneo »

saligne wrote: post #42
I_am_tiberius wrote: post #40

Everytime I read GrapheneOS news I search for news related to Fairephone. It's such a shame that there's still no official plan for Fairephone to work on requirements for GrapheneOS. The combination of those 2 would be fantastic. It would also open a big new market (I assume) for Fairephone so not sure why there seems no clear sign in that direction at all (to my knowledge).

You should search for the many times where GrapheneOS has stated they won't work with Fairphone

It's because Fairphone doesn't fulfil GOS's hardware requirements. If Fairphone addresses that, there's no reason for GOS to not support a Fairphone device.
Post reply on HN