Yeah. I'm not trying to be an apologist when I say there has to be some good reason why they went this route. I mean, it may not be a good reason to consumers, but there had to be some legitimate software/hardware engineering concerns that led them to look at multiple implementations and decide that the smartphone app was the way to go. I don't work in gaming or hardware design, but I work in development. I understand that sometimes it just happens that the client wants something and all we can offer in response is "we'd love to do it, but the solution isn't workable because of (insert reasons here)" or "we thought about that and could have done it, but unfortunately because (insert other reasons here) it was just more pragmatic to go this route."
I don't think the people working at Nintendo are big dumb dumb idiots that must be new to hardware and software engineering. But there's just no way that the teams were sitting around working on the basic, OS-level community functionality on the Switch itself, and it was working just fine, and then someone else came along and said "what about a smartphone app" and everyone agreed that this was definitely the more elegant approach and worth completely abandoning the console implementation for. What made putting these features on the console unworkable or a secondary priority? What challenges are they trying to overcome only offering a smartphone app?
Well this quote is only a few years old:
This was surprising to hear, as we would have thought that they had plenty of time to work on these features as it had been announced months before, so we probed a little deeper and asked how certain scenarios might work with the Mii friends and networking, all the time referencing how Xbox Live and PSN achieve the same thing. At some point in this conversation we were informed that it was no good referencing Live and PSN as nobody in their development teams used those systems (!) so could we provide more detailed explanations for them? My only thought after this call was that they were struggling - badly - with the networking side as it was far more complicated than they anticipated. They were trying to play catch-up with the rival systems, but without the years of experience to back it up.
It wouldn't exactly be shocking that they still have poor insight into how collective online services, and related functionality, should work and handed it off to DeNA in some fashion.