I’m not sure how much legacy code is written for contact apps in smartphones. But given the amount of tweaks and changes apple and Google make in each of their releases I would expect they wouldn’t have any problem integrating this feature.
Also you mentioned legacy code, but why T9 dialing isn’t a thing anymore coz that would be available if they were simply extending from legacy codebase.
But as someone who designs software I don’t immediately see any additional functionality. I’d like to understand the benefit to see if I want to incorporate the feature sometime
Alright I’ll provide a use case scenario. I wanted to this functionality when I was in uni where a lot of my contacts had more than one role to play and I had trouble remembering all the roles my contact would have. Let’s say one of my contact was my coursemate but also worked in organizing committee of an event. I knew other members of the organizing comittee as well. So in the event that I needed to share an information with the entire organizing committee, I needed to remember committee list members instead of software helping me. And what about another contact who also part of the event but was on a different team like Public Relations. You could say just another tag would suffice no need for nested ones. But this kind of events happens multiple times and I would have to create multiple tags for multiple events (instead of nesting) and it becomes cumbersome managing the list.
These kind of tags are supported in all kinds of note taking apps. I don’t think it would be an Hercularian task to achieve it.
Don’t underestimate the legacy code. There’s a reason we avoid it.
I’m not sure how much legacy code is written for contact apps in smartphones. But given the amount of tweaks and changes apple and Google make in each of their releases I would expect they wouldn’t have any problem integrating this feature.
Also you mentioned legacy code, but why T9 dialing isn’t a thing anymore coz that would be available if they were simply extending from legacy codebase.
I was just making a joke. Hopefully, those apps are not like the hardcoded messes that I’ve had to deal with before.
You’re right, it’s almost trivial.
But as someone who designs software I don’t immediately see any additional functionality. I’d like to understand the benefit to see if I want to incorporate the feature sometime
Alright I’ll provide a use case scenario. I wanted to this functionality when I was in uni where a lot of my contacts had more than one role to play and I had trouble remembering all the roles my contact would have. Let’s say one of my contact was my coursemate but also worked in organizing committee of an event. I knew other members of the organizing comittee as well. So in the event that I needed to share an information with the entire organizing committee, I needed to remember committee list members instead of software helping me. And what about another contact who also part of the event but was on a different team like Public Relations. You could say just another tag would suffice no need for nested ones. But this kind of events happens multiple times and I would have to create multiple tags for multiple events (instead of nesting) and it becomes cumbersome managing the list.
That’s awesome. I’d like to investigate it more…
You have the following contacts:
How would you like to tag them?