I think it is an uncommon use case, but I wouldn't say exotic. On the other hand, which of the latest services support it? WhatsApp doesn't, FaceTime doesn't (although they're rumored to soon). So I'd guess it isn't common enough to be launched in the initial versions.
On your second point, yes, you're segmenting by use case, I was segmenting by target customer.
It isn't "supporting only one video" that mean the target is consumer. Allo & Duo have no enterprise features, and are publicly marketed to consumers. Hangouts is marketed & sold as part of GSuite, the enterprise productivity suite from Google.
Targeting determines features, not the other way around.
> Hangouts is marketed & sold as part of GSuite, the enterprise productivity suite from Google.
And is embedded inside consumer Gmail, and included by default on every Android phone I've seen since it replaced Google Talk or GChat or whatever it replaced. It's the default SMS app on a lot of Android devices. What's enterprise about it?
> and included by default on every Android phone I've seen since it replaced Google Talk or GChat or whatever it replaced.
Hangouts has since been replaced by Messages as Google's primary Android SMS app, and by Allo as its primary Android internet-based text chat app, and by Duo as its primary Android video-call app.
target here is not a consumer, target here is particular feature. you fragmenting your target 'consumer' by video and text chats, each served by separate app. how is it not a use-case/feature segmenting?
feel free not to answer though
Nope, the target is the customer (consumer & enterprise), and then you build the features required by that customer.
You don't build a video calling tool and then look for a potential segment to sell it to, you define/find a segment and then build the product with the features required to target that segment.
it's not a 'consumer' target then, but a '1-on-1' use case => segmenting by use cases