Working with Images
Working with images, Icons and Launch Screens in Xamarin.iOS.
- PDF for offline use
- Sample Code:
- Related Articles:
- Related SDKs:
Let us know how you feel about this
last updated: 2017-03
This section includes a variety of articles that cover working with images in a Xamarin.iOS app, such as using them as icons, launch screens or including them in controls and providing icons for custom document types.
There are several ways that image assets are used inside an iOS app. From simply displaying an image as part of an app's UI to, assigning it to a UI control such as a
UIImageView, to providing icons and launch screens, Xamarin.iOS makes it easy to add great artwork to an iOS app in the following ways:
- Resolution Independent Images – Use iOS's built-in support for working with images across different device resolutions and types (iPhone, iPad, etc.).
- Asset Catalog Image Sets - Use Asset Catalog Image Sets to manage and group all version of a given image asset required by an app.
- Images in the iOS Designer - Use the iOS Designer to set images for controls.
- Images in Code – Use the
UIImageclass's methods to load and work with image assets and assign them to UI controls in C# code.
- Application Icon - Define the app icon required by every iOS app. This is the icon that the user will tap from the iOS home screen to launch the app. Additionally, this icon is used by Game Center, if applicable.
- Spotlight Icon - Define the app's Spotlight icon. Whenever the user enters the name of an app in a Spotlight Search, this icon is displayed.
- Settings Icon - Define the app's Settings icon. If the user enters the Settings app on their iOS device, this icon will be displayed at the end of the Settings list for the app.
- Launch Screens - Define the app's Launch Screen. After the user taps the app icon and before the first view appears, a blank screen will be shown. Fortunately, iOS includes support for displaying an image in place of the blank screen by using a Storyboard.
- iTunes Icon - Provide an iTune icon. If using the Ad-Hoc method of delivering an app (either for corporate users or for beta testing on real devices), the developer also needs to include a 512x512 and a 1024x1024 image that will be used to represent the app in iTunes.
- Document Icons - Use an image as an icon for any specific document type that a Xamarin.iOS app supports or creates.
Through a series of topics, this article shows how Xamarin.iOS takes full advantage of iOS to support image assets, all while handling the various device types and resolutions, and accomplish the tasks listed above.
There are several considerations that should be taken into account when creating image assets for an iOS app, as well as several places where those assets will be used. Each of these have an affect on not only how many image assets will be required, but how those assets are created. The following topics cover the types of images assets that will be required, how those assets are included in the application's bundle and how the image assets are consumed to provide the required functionality:
This article covers including an image asset in a Xamarin.iOS app and displaying that image either by using C# code or by assigning it to a control in the iOS Designer.
This article covers including and managing an image asset in a Xamarin.iOS app to be used as an App Icon.
Apple has added several enhancements to iOS 10.3 that allow an app to manage its icon:
ApplicationIconBadgeNumber- Gets or sets the badge of the app icon in the Springboard.
truethe app has an alternate set of icons.
AlternateIconName- Returns the name of the alternate icon currently selected or
nullif using the primary icon.
SetAlternameIconName- Use this method to switch the app's icon to the given alternate icon.
This article covers using a special type of Storyboard to provide a universal Launch Screen for every iOS device size and resolution.
This article covers including and managing an image asset in a Xamarin.iOS app to be used as a Custom Document Type Icon.
This article covers several deprecated image technologies and technique that might be required to maintain an older Xamarin.iOS app. Whenever possible, any existing apps should be updated to move away from these technologies, as they may be dropped by Apple in future iOS releases.