I don't know if it's only me that have a form to be filled with contact information. Passing through my app, I can build geoqueries of nearby clients and build a lot of app specific behavior for each contact information. Today I must offer a one-click option to save that same info as a new contact - the user should not type it again. As I see, this great API is for reading contacts only, and I am sure you have huge reasons for it to be like this.

Ok!

In this case, what about letting the user create a contact in his/her own cellphone - with no forms,
using the interface he/she knows well! - and, only then, my app could know and read this specific newly added contact, with consent from the user. And voilà: as before, both the user's phone AND my app have, both, the contact info we all love and need. In this scenario contact is inserted first, then my app reads after. Instead of my app creating a contact inside one more custom form and, then, do a miracle to help the user save the contact without retyping.

I would "call" the contacts for the user and, blindly, wait for a "new and last" inserted contact, say, during a timeout maybe, for more protection (I am being inspired by the SMS API way to preserve security). This would let the user be where he/she loves - his/her own contacts interface - while still inserting a contact that I would be allowed to see right after completed. If this is a "nice" idea, we could think a way to update this same contact information (user saves it but adds one more phone right after, for instance - should this update create an event reachable from my app again? Why not?, actually. Maybe restricted by a timeout, like SMS API).

I know you'll forgive me if there is already a clever way to do this, with my suggestion being irrelevant in this case. I apologize in advance for any mistake in this huge web and programming ecosystem. In any case: a huuuge thanks for the great advances, fast and efficient, you are being able to deliver so well. You're HUGE.