Add ‘home’ [and maybe ‘open’ as an alias] command

[danielbayley]

Similar to #26, which is being implemented in #55. Maybe this would need to be built on that work actually…

The URI scheme is basically just macappstore://itunes.apple.com/{region}/app/{name}/id{id}.

So usage could be for example mas home 904280696, which would call something like macappstore://itunes.apple.com/{region}/app/things-3/id904280696?mt=12.

[phatblat]

@danielbayley I'm looking into implementing this and have a question for you. What do you think about both a home and open command? home would open the page in a browser and open would open the app page in the App Store app.

• home: https://itunes.apple.com/us/app/things-3/id904280696?mt=12
• open: macappstore://itunes.apple.com/us/app/things-3/id904280696

sellerUrl

Another URL to consider (instead of the MAS Preview URL) is the sellerUrl attribute which appears to be the link behind the "Developer's Website" button.

MAS Preview

MAS App

"Website" link to the right of app description:

Below reviews and information:

However, Things is a bad example because this ends up redirecting users to the Mac App Store.

1. sellerUrl -> https://culturedcode.com/things/mac/
2. 302 redirect -> https://culturedcode.com/things/mac/appstore/
3. HTML "refresh" -> <meta http-equiv="refresh" content="0; url=https://itunes.apple.com/us/app/things-3/id904280696?mt=12&amp;ls=1">
4. Mac App Store Preview -> https://itunes.apple.com/us/app/things-3/id904280696?mt=12

In the case of Notability this sellerUrl points to http://www.gingerlabs.com which is a great example of an app site.

[danielbayley]

@phatblat I think separate home and open commands for those would work well… and maybe sellerUrl could be a third vendor (consistent with Homebrew parlance) command also?

[phatblat]

This is out now in 1.6.0