# All channels
317: Crafting Great Reverse-DNS Identifiers 🆔September 21, 2017 at 6:15pm (Edited 3 years ago)
Apple platforms make heavy use of "reverse-DNS" identifiers.
They appear everywhere from our Application's Identifier all the way down to the Dispatch Queues we create in our code.
These identifiers are somewhat opaque in a conceptual sense, and have been around in programming for many years.
We create or set them once, and sometimes reference them in our code, but the main idea is that they're a unique, human-readable way to identify some unique "thing". Their nature also offers the benefit of being unlikely to "collide" with one another.
The first thing we'll want to define is some kind of top level prefix to put on all our identifiers.
Fun Fact: Historically these identifiers were literally reversed-DNS. That is to say, to form one in code we might take our website's domain name, reverse it, then append our app's name (for example). These days, on Apple platforms, this isn't really a "thing" anymore. Now, we're usually given a string property or text field where we can supply just about any value we want.
This means that the common TLD's on the internet are also commonly used here. A company may begin all of their identifiers with com., while a non-profit may start theirs with org..
Next, we'll want to think of some way to group all of our identifiers, across all of our apps.
Often this is a domain-style version of our company or organization's name, or perhaps simply our own name, all lowercased, with no punctuation.
Pro Tip: Identifiers can contain numbers, letters, hyphens (-), and dot (.) characters. Hi! Bundle ID can have hyphens, not underscores. They're also case-sensitive. (Thanks to reader @pointum for the tips here!)
This gives us something like com.littlebites.
Great. Now we can apply this wherever we need to identify things.
Here are a few examples:
Applications and Extensions
com.littlebites.reader - An identifier for an imaginary app to read Bites. We might be tempted to just use com.littlebites.app or something generic, but this way we leave ourselves open to the possibility of making other apps in the future.
In-App Purchase Identifiers
With these, we want to think about the complete set of In-App Purchases we plan on offering and create groups within them if possible. com.littlebites.reader.subscriptions.monthly, com.littlebites.reader.subscriptions.yearly - Here we have an imaginary subscription plan In-App Purchase.
We know we want to offer other types of In-App Purchases in the future, so we've "grouped" all subscription purchases under a subscriptions. segment. Then we're able to add a shorter phrase denoting the type as the final segment.
App Groups help us share data between our apps or our app's extensions.
group.com.littlebites.cache, group.com.littlebites.user - Apple encourages to begin these with the group.. This way we know right away what we're dealing with. Here we've created two app groups, one to share less-important cache data (images, etc.) between apps while we sort of "wall-off" user data into it's own group.
That's all for now, have a tip or some advice about these identifiers that to share? Send it to [email protected].
This post is made possible thanks to the support of BuddyBuild 🙌
Check them out and start building better apps for free today: buddybuild.com