6 ms·

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 al

by mrd3v0 5d ago

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.

subscribed 5d ago
What? :) You mean the perfectly functional (if barebones) AOSP call app? :)
- gpvos 5d ago
  The one with the terrible UI, yes.
- HybridStatAnim8 5d ago
  It will get ported to kotlin, material 3, and jetpack compose, just like Messaging.
okanat 5d ago
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.
- azdle 5d ago
  Can confirm the same works on Graphene. Also works directly from the "Recents" list.
loufe 5d ago
This is completely false. Tap the call, tap "call details" and its there. Took be 2 second to disprove. This is lazy to the point of being seemingly malicious commentary.
- j1elo 5d ago
  I'm just reading from the barrier here, and not knowing what it even looks like, but reading your description I can immediately agree that it is a bad design. There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time. 2 taps for some other extra info such as call length, or further contact details, would be OK I guess, but for first-level info as these, it's 100% bad design. I mean come on, design-wise this was already a "Done" thing in the golden Nokia days! https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n85-smartphone-day-1-2/ https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n... [*] Ctrl+F to find the image below "miss a call".
  - fc417fc802 5d ago
    > design-wise this was already a "Done" thing in the golden Nokia days! I might be mistaken but I seem to recall it being a done thing for android prior to several years ago when it was "improved" with an update. Although it's possible I'm confusing the call apps from AOSP and various vendors. Either way several of my past android devices had a significantly better address book, dialer, and call history.
  - Walf 5d ago
    >not knowing what it even looks like Clearly. >There's only a handful of critical details in a call history And they're all there: profile pic, contact name, indicators that show incoming/outgoing + missed/connected, which SIM, a redial button, how long ago (which after about a week shows the date), Tapping the middle expands the row (no obstructive pop-up) to show Block, Message, & Details buttons. The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. Tapping the Details will show all calls in that group, whether it's one or seven, with their full dates, times, durations, and further options. It's never been a difficult UX.
    - kwarcode 5d ago
      > The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. But a precise time does always make sense. And even if "doesn't always make sense" was true, it doesn't on its own justify a different default. So what does grouping have to do with it?
HybridStatAnim8 5d ago
Good news! GrapheneOS has ported Messaging to kotlin, jetpack compose, and material you. The same is planned for the Contacts app, Dialer app, and more. Dont quote me but it seems Contacts and Dialer are up next after Messaging. Also, GrapheneOS has very recently released automatic call recording for the Dialer.

by mrd3v0 5d ago

subscribed 5d ago

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

gpvos 5d ago
The one with the terrible UI, yes.
HybridStatAnim8 5d ago
It will get ported to kotlin, material 3, and jetpack compose, just like Messaging.

okanat 5d ago

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.

azdle 5d ago
Can confirm the same works on Graphene. Also works directly from the "Recents" list.

loufe 5d ago

This is completely false. Tap the call, tap "call details" and its there. Took be 2 second to disprove. This is lazy to the point of being seemingly malicious commentary.

j1elo 5d ago
I'm just reading from the barrier here, and not knowing what it even looks like, but reading your description I can immediately agree that it is a bad design. There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time. 2 taps for some other extra info such as call length, or further contact details, would be OK I guess, but for first-level info as these, it's 100% bad design. I mean come on, design-wise this was already a "Done" thing in the golden Nokia days! https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n85-smartphone-day-1-2/ https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n... [*] Ctrl+F to find the image below "miss a call".
- fc417fc802 5d ago
  > design-wise this was already a "Done" thing in the golden Nokia days! I might be mistaken but I seem to recall it being a done thing for android prior to several years ago when it was "improved" with an update. Although it's possible I'm confusing the call apps from AOSP and various vendors. Either way several of my past android devices had a significantly better address book, dialer, and call history.
- Walf 5d ago
  >not knowing what it even looks like Clearly. >There's only a handful of critical details in a call history And they're all there: profile pic, contact name, indicators that show incoming/outgoing + missed/connected, which SIM, a redial button, how long ago (which after about a week shows the date), Tapping the middle expands the row (no obstructive pop-up) to show Block, Message, & Details buttons. The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. Tapping the Details will show all calls in that group, whether it's one or seven, with their full dates, times, durations, and further options. It's never been a difficult UX.
  - kwarcode 5d ago
    > The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. But a precise time does always make sense. And even if "doesn't always make sense" was true, it doesn't on its own justify a different default. So what does grouping have to do with it?

HybridStatAnim8 5d ago

Good news! GrapheneOS has ported Messaging to kotlin, jetpack compose, and material you. The same is planned for the Contacts app, Dialer app, and more. Dont quote me but it seems Contacts and Dialer are up next after Messaging. Also, GrapheneOS has very recently released automatic call recording for the Dialer.