forked from intentkit/IntentKit
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
bff6bb0
commit ffb08bf
Showing
3 changed files
with
36 additions
and
147 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,7 +8,7 @@ MWOpenInKit is an easier way to handle third-party URL schemes in iOS apps. | |
|
|
||
| Linking to third-party apps is essentially broken on iOS. Let's say that, as a developer, you want to allow users to open map links in Google Maps instead of the built-in Maps.app. You now need to write a whole bunch of custom code that determines whether Google Maps is installed, ask the user which they would prefer, and ideally remember that preference. | ||
|
|
||
| If we take a more complex example, like Twitter clients, you're now potentially managing a dozen different third-party URL schemes that are all drastically different and most likely poorly-documented. | ||
| If we take a more complex example, like Twitter clients, you're now potentially managing a dozen different third-party URL schemes that are all drastically different and quite possibly poorly-documented. | ||
|
|
||
| As a result, very few apps link to external third-party apps for tasks handled by Apple's easier-to-link-to apps, even when users prefer third-party apps. | ||
|
|
||
|
|
@@ -95,20 +95,20 @@ Extending MWOpenInKit to include your own application's URL scheme is easy. | |
|
|
||
| 2. Inside that directory, create a plist. Its name should be the name you want displayed, and it should contain a dictionary. Each key is the signature of a method in the appropriate `MWHandler` object, and the key is a template string used to generate a URL for that method, where variables wrapped in `{handlebars}` will be interpolated at runtime. | ||
|
|
||
| As much as possible, the template variable keys are named the same as the parameter names of the corresponding Objective-C methods, but there's nothing enforcin that. I'd recommend looking at other plist files in the directory to see what the correct method keys and template keys are. | ||
| As much as possible, the template variable keys are named the same as the parameter names of the corresponding Objective-C methods, but there's nothing enforcin that. I'd recommend looking at other plist files in the directory to see what the correct method keys and template keys are. | ||
|
|
||
| 3. Your app's icon goes in the same directory. You will need four copies of the icon, all with the same root name as your plist file: | ||
|
|
||
| - `AppName.png`: 60x60 | ||
| - `[email protected]`: 120x120 | ||
| - `AppName-iPhone.png`: 76x76 | ||
| - `[email protected]`: 152x152 | ||
| - `AppName.png`: 60x60 | ||
| - `[email protected]`: 120x120 | ||
| - `AppName-iPhone.png`: 76x76 | ||
| - `[email protected]`: 152x152 | ||
|
|
||
| These will all be shown as-is, so they should be prerendered. The root filename ("AppName" in those examples) must exactly match the filename of the plist. | ||
| These will all be shown as-is, so they should be prerendered. The root filename ("AppName" in those examples) must exactly match the filename of the plist. | ||
|
|
||
| 4. Submit a pull request! There is no need to manually add any of the files to Xcode. | ||
|
|
||
| Make sure to try it out first using the demo app to make sure that it works. If this project becomes sufficiently popular, it is likely I'll build a linting tool. | ||
| Make sure to try it out first using the demo app to make sure that it works. If this project becomes sufficiently popular, it is likely I'll build a linting tool. | ||
|
|
||
|
|
||
| Contact | ||
|
|
||