There seems to be a lot of 'reaching' here about usability (pun intended) that discounts the problem can be solved multiple ways with the phone. The focus seems to be overwhelmingly on how to use a phone as a dumb device to replicate a keyfob, where there is a lot more you can do just within the interface of the phone to address different scenarios that a keyfob couldn't even get close to.
One just off the top of my head is I walk up to the car and unlock my phone (with an iPhone a single button press) where the app recognizes it's my car I walked up to, unlocks the driver door and pops up a prompt on screen for a second button press to unlock all doors. Hell they could even use an Apple Watch in place of a keyfob. There is probably also ways to do other things with a software based interface we haven't even thought of yet.
As to the kid problem, the above would directly address that too, just reach in your pocket and two button presses then you're putting the kid in. I think most of the griping about using a phone is missing an important bit, you can do _much_ more with a software interface to solve issues like this than you can with a static piece of hardware like a fob. It doesn't _have_ to be limited to just the phone either as a companion bit like a watch would extend what you could accomplish. The only thing you're losing is that you're used to how a keyfob works, so it's simple and familiar to you.