In iOS app development, I’ll summarize my research on the client app name “via iOS” display for Twitter tweets using Social.framework.

First, the “via iOS” part seems to have the following specifications:

When Using Social.framework (since iOS6) / Twitter Framework (iOS5)

When tweeting using iOS standard features via Social.framework, the “via iOS” part cannot be changed.

After release, the app name and iTunes Store URL seem to be automatically attached.

In development or AdHoc versions, it appears to remain as “via iOS” display.

It looks like you can't actually set this.

According to: https://dev.twitter.com/issues/39 They match based on the app name in Apple’s database. You can’t already have a registered Twitter Application with the same name.

Also, seems that you can’t get this to work with AdHocs or test apps, only published apps.

[Quote]: How can I sign tweets containing my custom “via” with the iOS 5 Twitter framework? - Stack Overflow

When Using API

When logging into Twitter via API to tweet, the “via iOS” part can be freely configured.

For example, if you’re releasing both iOS and Android versions of an app, you’d want to set the “via xxx” link to your app’s landing page URL rather than the iTunes Store URL.

Summary

■ Tweet with iOS Standard Features [Advantages] ・Can tweet directly with Twitter accounts set on the device (No need to go through login process)

[Disadvantages] ・“via xxx” URL is always iTunes Store URL ・Makes it difficult for Android users to download the app

■ Tweet via API [Advantages] ・Can specify “via xxx” URL

[Disadvantages] ・Need to login when tweeting for the first time

That’s all from the Gemba.