Re:Show HN: WhatsApp for Desktop
by amyjess on Monday June 22, 2015 @10:48AM
(#9758677)
"[Name] for [Service]" is a popular format in the third-party client world, and it's one that's tolerated by all the big players.
Much older examples include "Plume for Twitter" and "FriendCaster for Facebook". In the case of the former, it was by agreement with Twitter: Plume used to be called Touiteur until Twitter made them change it.
You're seeing it more lately because Google recently changed the Play Store's app naming policy to forbid using the name of an existing service as part of your app's main brand, only allowing a special clause (e.g. "for [Service]") following the main brand. Also, around the same time, reddit changed their API policy to add a similar requirement.
In the long run, it's going to be beneficial for app developers because now they can take their name and use it for apps across multiple services. For example, the developers of Plume could create a "Plume for Facebook" app and so on, so they end up with a whole family of Plume apps, each one for a different social network.
Much older examples include "Plume for Twitter" and "FriendCaster for Facebook". In the case of the former, it was by agreement with Twitter: Plume used to be called Touiteur until Twitter made them change it.
You're seeing it more lately because Google recently changed the Play Store's app naming policy to forbid using the name of an existing service as part of your app's main brand, only allowing a special clause (e.g. "for [Service]") following the main brand. Also, around the same time, reddit changed their API policy to add a similar requirement.
In the long run, it's going to be beneficial for app developers because now they can take their name and use it for apps across multiple services. For example, the developers of Plume could create a "Plume for Facebook" app and so on, so they end up with a whole family of Plume apps, each one for a different social network.