lobsterghost1 wrote:
tanurag wrote:
Even i don't know after getting that much of complaints why apple didn't took any action or repair regarding this technical issue/error?
Likely because Apple doesn't believe this is an issue and it's working as they intend it to work.
Even if Apple was considering changes to the behavior, most companies who were looking at changes like this would not implement them instantly.
The change that people here want is a feature request. And it's one that potentially interacts with other features that Apple and its customers would want to maintain, like the ability to use a Mac to place or receive phone calls with the aid of a nearby iPhone. If Apple is considering changes, I hope they're taking their time to think through the interactions of related features in various cases – not just the case of two iPhones with the same Apple ID.
If Apple management decided to add the requested feature (NOTE CAREFULLY: I am NOT saying, or speculating, that they have), it would still take time to
- Try to separate out the real requirement from all of the broken implementations stated as requirements
- Clearly document the requirement
- Come up with prototype designs for implementing the requirement
- Think through how these designs would interact with related features
- Determine what changes needed to be made to the code base
- Make those code changes
- Test the code
- Build a new release of iOS
- Run through the process for documenting the release and distributing it to the entire world
That's the way software development works for products that have huge numbers of users. Even something that involves a very small, low-risk change to the code base may take a LONG time to work its way to a release – once you consider all of the steps meant to filter out bugs ("release in haste; repent at leisure").
Plus, do you think that Apple only works on one iOS feature or bug at a time? For software like this, there will be many code changes, for many different things, going on at the same time. Release management won't be about just selecting and testing one feature/fix, but about selecting and testing a whole bunch of them. If any of those are incomplete, or are insufficiently tested, or have fatal bugs, that could hold up an entire release, including the changes that work just fine, but aren't in customer hands yet.