[Dialer] ubuntu touch bad dialer/contacts integration
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu UX |
Opinion
|
Wishlist
|
Olga Kemmet | ||
| dialer-app (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I' using my ubuntu phone as a telephone mostly! I find it somewhat annoying, how much steps have to be taken to select a contact from contacts. These are the steps:
1) Hit Contacts
2) Hit the magnifying glass
3) Enter filter string
4) Select contact
5) Select number
6) Hit the green Button.
This is 6 Buttons - as much as a telephone number has (in Austria)
I'd like to have a filter field in the dialer app, with contacts popping up as I enter the filter string. Contacts should be shown in a tree view with the numbers visible. If I hit a number, it will be dialed immediately.
A bit the same, when using the 'recent' view of the dialer or favourites. If you select a call, it won't be dialed immediately. The number is transferred to the dialer field and you have to hit the green button.
PS: I'd like to contrubute to the touch project. I'm a software developer (mostly doing C/C++/Qt). If someone would guide me, I'd do some work.
| affects: | launchpad → dialer-app |
| affects: | dialer-app → dialer-app (Ubuntu) |
| summary: |
- ubuntu touch bad dialer/contacts integration + [Dialer] ubuntu touch bad dialer/contacts integration |
| Changed in ubuntu-ux: | |
| status: | New → Triaged |
| assignee: | nobody → Olga Kemmet (olga-kemmet) |
| importance: | Undecided → High |
| tags: | added: usability |
| Olga Kemmet (olga-kemmet) wrote | #1 |
| Changed in ubuntu-ux: | |
| importance: | High → Wishlist |
| status: | Triaged → Opinion |
| importance: | Wishlist → Low |
| importance: | Low → Wishlist |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in dialer-app (Ubuntu): | |
| status: | New → Confirmed |
| maarten klop (mjdklop) wrote | #3 |
| Felix Wilke (felixw83) wrote | #4 |
Thanks for filing this bug. Unfortunately this is more of a feature request/usability issue than a bug. As much as I do understand the reported problem here, the behaviour is not "broken". Design will have to address this issue at a later stage in the project.