DoubleDutch FAQs
DoubleDutch's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 355 most popular questions DoubleDutch receives.
Frequently Asked Questions About DoubleDutch
The Attendees section in the CMS can be used to add your attendees to your event in the app. Items added in this section must include a first and last name, email address, password, and can be tied to agenda sessions for personal agendas.
welcome email
Click one of the Guide Me buttons below for a guided walkthru of attendees!
US
EU
Adding Attendees
Click on the Content tab in the CMS, and then click on the attendee section from the menu to start working with attendees.
From the attendee list screen in the CMS, you can add attendees in two ways:
Add a single Attendee:click the ‘Add Attendees’ button at the top, click 'Add single attendee', and fill out the fields. The first and last name, email address, and password are required fields.
Import multiple Attendees:click the ‘Add Attendees’ button at the top, download the import template, fill it out, and then upload that same template by clicking ‘Import Excel or CSV’.
Learn how to import attendees from Eventbrite.
Importing Attendees in Bulk
Here are the guidelines you will need to follow to fill out the template correctly. Required fields are listed in bold. For any columns that you are not filling in data, just leave them blank on the template. Please DO NOT delete or modify any column, including the headers, or the import will not work.
Field
Example / Data Format /Best Practice
Character Limit
First Name
Lawrence
50
Last Name
Coburn
50
Email Address
150
Password
The password needs to bea minimum of 6 characters - can be letters and/or numbers.
e.g. 123456 (or) Generic1
150
Title
CEO
500
Company
DoubleDutch
500
Biography
Plain text, attendees cannot edit.
4000
Phone Number**
(415) 867-5309
50
Image URL
https://example.com/profilephoto.jpg
Images should be a minimum of 256x256 PNG or JPG, and must be hosted with public access
2000
Address**
123 Main St
Apartment B
San Francisco, CA 94110
USA
Address Field 1: 400char
Address Field 2: 400char
City: 50char
State: 50char
Postal Code: 100char
Country: 100 char
Attendee ID
Attendee001
500
Groups
Comma Separated
Designate any number of groups; great for push notifications
100
Personal Agenda
Please refer to this article for info on working with personal agendas
Session002, Session002
Exhibitor ID
If this person is associated with an Exhibitor, enter Exhibitor ID in this field
e.g. Exhibitor083
500
Exhibitor Role
Admin or Booth Staff
If you don’t enter Admin, Booth Staff will be assumed.
For more info on these roles, click here
Speaker ID
If this person is associated with a Speaker, enter Speaker ID in this field
e.g. Speaker083
500
Variable Data**
3 fields to fill in any attendee data that there is not a dedicated space for in the profile already (e.g. Department, Customer ID, Industry, Region)
500 in each of the 3 fields
Hide in Mobile App*
Hidden attendees will not be displayed within the attendee list, global search results, upcoming session reminder cards, or user recommendations. However, hidden attendees will still be visible on exhibitor profiles if they are listed as booth staff.
yes or blank
*Note: If a hidden attendee engages in an activity which exposes them to other attendees, their profile card will become visible via that route (e.g. if a hidden user messages Joe, then Joe will see the hidden user's profile; if a hidden user posts to a Topic Channel, then everyone who enters the Topic Channel will be able to see the hidden user's profile, etc.)
**Note: Attendee contact information and the data in variable fields will not be displayed in the app. If you have lead scanning enabled for your event, attendee phone numbers and addresses, as well as the data in the three variable fields, will display in the leads report.
To randomly generate passwords, use the function "=randbetween(100000,999999)" in the password column.To find all of your IDs for exhibitors, sessions, and speakers already entered into the CMS,you can download the Content Lists file from the Exportable Reports section of the Event Performance tab in the CMS.
To import the file after you have completed all the sections:
Click the 'Add Attendees' button from the Attendee list.
Select 'Import Excel or CSV' from the drop-down, then select your file, and click 'open'. Supported file types for import include .csv (encoded in UTF-8), .xls (Microsoft Excel 1997-2004), .xlsx (Microsoft Excel 2007 and beyond).
That will then take you to the import preview where you can see the summary. If this information is correct, click 'Save & Continue' and the import will process.
Note: if you accidentally list a session more than once in the same attendee's personal agenda on the template, you will receive a "duplicate identifier" error on the Summary page. Once you remove the duplicated session ID, you can import your template.
Updating Attendee Information via Import
Once your initial attendee template has been imported, you can continue to edit and update your attendees via imports:
From your attendee list, click the 'Actions' drop-down.
Select 'Export Data' from the drop-down to export a .xlsx, .csv, or .xls file of your most up-to-date attendee information in the CMS.
Add any additional attendee info to the template, but please note the following:
Attendee passwords cannot be updated via the import template, and you will need to leave this column with "[cannot export- leave this when updating]".
For updates to attendee personal agendas, you can add/remove session unique IDs in the Personal Agenda column of the template.
You will need to list alldesired sessions in the attendees' personal agendas as the importer supports "de-linking" for personal agendas (meaning it will remove all sessions from the attendee's profile in the CMS that are not listed in the most recent import template).
Save your changes to the updated template and re-import in the CMS.
Note: If you accidentally list a session more than once in the same attendee's personal agenda, you will receive a "duplicate identifier" error on the Summary page. Once you remove the duplicated session ID, you can import your template.
Attendee Actions in the CMS
Selecting an attendee will activate the ‘Actions’ menu, from which you can:
Clear Points:reset the attendee's points to zero. Their activity and profile will not be affected.
Clear Activity:remove all activity from the attendee’s profile and the feed (comments, survey responses, and photos), including points and achievements earned. Their profile will not be affected, and bookmarks and sessions in 'My Agenda' will remain in tact.
Hide in Mobile App: hides the attendee from the attendee list. See the disclaimer mentioned above for rules around this feature.
Show in Mobile App: makes the attendee unhidden from the attendee list.
Delete:delete theuser from the database.
Reset Password:randomly generate a 6-digit password (displayed in a pop-up). You will then need to notify the attendee directly (notification will not be automatically sent).
Set ALL Attendees' Passwords:set the password for all attendees present in this event to a new default password that they will use to log into the app.
Send WelcomeEmail:send selected users the default .
Send Welcome Email to Non-Active:send welcome email to users who have not logged in yet.
Send WelcomeEmail to ALL:send welcome email to your entire attendee list.
Export Data:download a .xlsx, .csv, or .xls file of all the information you’ve added to the attendeelist.
Note: by highlighting more than one attendee, you can perform the same action on multiple attendees.
View ArticleThe Agenda section in the CMS can be used to add sessions to your event in the app. Items added in this section can include a name, start and end times, filters and tracks, and can be tied to speakers.
Filters
Click one of the Guide Me buttons below for a guided walkthru of agenda sessions!
US
EU
AddingAgenda Sessions
Click on the Content tab in the CMS, and then click on the agenda section from the menu to start working with agenda sessions.
From the agenda screen in the CMS, you can add agenda sessions in two ways:
Add a single Agenda Session:click the ‘Add Session’ button at the top, click 'Add single session', and fill out the fields. The name, and the start and end time, of the session, are required fields.
Import multiple Sessions:click the ‘Add Session’ button at the top, download the import template, fill it out, and then upload that same template by clicking ‘Import Excel or CSV’.
Importing Agenda Sessions via the Template
Here are the guidelines you will need to follow to fill out the template correctly. Required fields are listed in bold. For any columns that you are not filling in data, just leave them blank on the template. Please DO NOT delete or modify any column, including the headers, or the import will not work.
Note: if you need to use special characters in your content import, please reference our article on text formatting with Excel.
Field
Example / Data Format / Best Practice
Character Limit
Session Name
Plain Text
e.g. Welcome Reception
250
Description
Text and images
15000
Start Time
Month/Day/Year 8:00 AM
NA
End Time
Month/Day/Year 9:00 AM
NA
Location
Room 101
45
Session Tracks
Comma-separated
e.g. Marketing, Sales, IT
60 each
Filters
Create in CMS before import
Comma-separate in template
e.g. keynote, breakout session, reception
60
Speaker IDs
Comma-separated
e.g. Speaker002, Speaker017, Speaker025
500
Link URLs
Hosted file URLs or relevant links to this session that you want to share on the details page
https://www.example.com/exampledocument.pdf
2000
Session ID
Session001
500
Note: all URLs must include https:// to ensure that attendees can access the websites or hosted documents.
To find all of your IDs for speakers already entered into the CMS,you can download the Content Lists file from the Exportable Reports section of the Event Performance tab in the CMS.
To import the file after you have completed all the sections:
Click the 'Add Session' button from the Agenda list.
Select 'Import Excel or CSV' from the drop-down, then select your file, and click 'open'. Supported file types for import include .csv (encoded in UTF-8), .xls (Microsoft Excel 1997-2004), .xlsx (Microsoft Excel 2007 and beyond).
That will then take you to the import preview where you can see the summary. If this information is correct, click 'Save & Continue' and the import will process.
Note: Session Tracks will be created automatically upon import. Session must be created in the CMS prior to import and then entered into the template. It is usually easier to create and attach filters in the CMS all-together.
Updating Agenda Sessions via Import
Once your initial agenda sessions template has been imported, you can continue to edit and update your sessions via imports:
From your agenda list, click the 'Actions' drop-down.
Select 'Export Data' from the drop-down to export a .xlsx, .csv, or .xls file of your most up-to-date sessions information in the CMS.
Add any additional session info to the template.For updates to tracks and/or filters, you will need to listalldesired tracks/filters on the agenda template as the importer supports "de-linking" for session tracks/filters (meaning it will remove all tracks/filters from the session in the CMS that are not listed in the import template).
Save your changes to the updated template and re-import in the CMS.
View ArticleThe Speakers section in the CMS can be used to add speakers to your event in the app. Items added in this section can include a name, image and bio, social media links, and can be tied to agenda sessions.
Click one of the Guide Me buttons below for a guided walkthru of adding speakers!
US
EU
AddingSpeakers
Click on the Content tab in the CMS, and then click on the Speakers section from the menu to start working with speaker items.
From the speakers screen in the CMS, you can add speakers in two ways:
Add a single Speaker:click the ‘Add Speaker’ button at the top, click 'Add single speaker', and fill out the fields. The first and last name of the speaker are required fields.
Import multiple Speakers:click the ‘Add Speaker’ button at the top, download the import template, fill it out, and then upload that same template by clicking ‘Import Excel or CSV’.
Note: if you want your speakers to have access to your app, you'll also need to add your speaker as an attendee.
Importing Speakers via the Template
Here are the guidelines you will need to follow to fill out the template correctly. Required fields are listed in bold. For any columns that you are not filling in data, just leave them blank on the template. Please DO NOT delete or modify any column, including the headers, or the import will not work.
Field
Example / Data Format /Best Practice
Character Limit
First Name
Lawrence
250
Last Name
Coburn
250
Title
CEO
100
Company
DoubleDutch
100
Description
Text and images
15000
Image URL
https://example.com/lawrencecoburn.jpg
Images should be 560x620 PNG or JPG
2000
Website
https://doubledutch.me
2000
Twitter Handle
@DoubleDutch
15
Facebook URL
https://facebook.com/playDoubleDutch
2000
LinkedIn URL
https://linkedin.com/company/doubledutch
2000
Session ID
Session001
500
Attendee ID
The speaker’s ID from the Attendee profile
Attendee001
500
Speaker ID
Speaker001
500
Note: all URLs must include https:// to ensure that attendees can access the websites or hosted documents.
To find all of your IDs for sessions and attendeesalready entered into the CMS,you can download the Content Lists file from the Exportable Reports section of the Event Performance tab in the CMS.
To import the file after you have completed all the sections:
Click the 'Add Speaker' button from the Speaker list.
Select 'Import Excel or CSV' from the drop-down, then select your file, and click 'open'. Supported file types for import include .csv (encoded in UTF-8), .xls (Microsoft Excel 1997-2004), .xlsx (Microsoft Excel 2007 and beyond).
That will then take you to the import preview where you can see the summary. If this information is correct, click 'Save & Continue' and the import will process.
Updating Speakers via Import
Once your initial speaker template has been imported, you can continue to edit and update your speakers via imports:
From your speaker list, click the 'Actions' drop-down.
Select 'Export Data' from the drop-down to export a .xlsx, .csv, or .xls file of your most up-to-date speaker information in the CMS.
Add any additional speaker info to the template.
Save your changes to the updated template and re-import in the CMS.
View ArticleThe Exhibitorssection in the CMS can be used to add exhibitors and/or sponsors to your event in the app. Items added in this section can include a name, image and description, social media links, and can be tied to an interactive map. If an email address is entered, attendees will also be able to tap a link to request information from that exhibitor via email.
You can also assign exhibitors to different categories or filters if you want attendees to be able to easily sort through a long list.
Click one of the Guide Me buttons below for a guided walkthru of adding sponsors/exhibitors!
US
EU
Adding Exhibitors
Click on the Content tab in the CMS, and then click on the Exhibitorssection from the menu to start working with exhibitoritems.
From the sponsors or exhibitorsscreen in the CMS, you can add exhibitors in two ways:
Add a single Exhibitor/Sponsor:click the ‘Add Exhibitor’ button at the top, click 'Add single exhibitor', and fill out the fields. The name of the exhibitor is a required field.
Import multiple Exhibitors/Sponsors:click the ‘Add Exhibitor’ button at the top, download the import template, fill it out, and then upload that same template by clicking ‘Import Excel or CSV’.
Importing Exhibitors via the Template
Here are the guidelines you will need to follow to fill out the template correctly. Required fields are listed in bold. For any columns that you are not filling in data, just leave them blank on the template. Please DO NOT delete or modify any column, including the headers, or the import will not work.
Field
Example / Data Format /Best Practice
Character Limit
Exhibitor Name
DoubleDutch
250
Description
Text and images
15000
Categories*
Comma-separate
e.g. Events, Software
60
Filters*
Create unlimited Filter Groups and Filters in CMS. Comma-separate in the template.
60
Exhibitor Staff
Attendee IDs for boothstaff for this exhibitor
e.g. Attendee001, Attendee003
Booth Name
If you've already created an interactive map in the CMS and labeled your booth numbers, you can link the exhibitor to that booth by filling in the # in this column.
e.g. 217
50
Website
https://doubledutch.me
2000
Twitter Handle
@DoubleDutch
15
Facebook URL
https://facebook.com/playDoubleDutch
2000
LinkedIn URL
https://linkedin.com/company/doubledutch
2000
Phone Number
(800) 748-9024
100
Email Address
50
Targeted Offers Access
No longer in use.DO NOT USE
on/off
Lead Scanning Access
Set whether or not each exhibitorwill have access to lead scanning in their app.
on/off
Image URL
https://example.com/exhibitorlogo.jpg
Images should be a minimum of 256x256 in PNG or JPG
Exhibitor ID
Exhibitor001
300
*Categories will be created automatically in the CMS upon import. Filter groups and filters need to be created manually in the CMS prior to import.
Note: all URLs must include https:// to ensure that attendees can access the websites or hosted documents.
To import the file after you have completed all the sections:
Click the 'Add Exhibitor' button from the exhibitor list.
Select 'Import Excel or CSV' from the drop-down, then select your file, and click 'open'. Supported file types for import include .csv (encoded in UTF-8), .xls (Microsoft Excel 1997-2004), .xlsx (Microsoft Excel 2007 and beyond).
That will then take you to the import preview where you can see the summary. If this information is correct, click 'Save & Continue' and the import will process.
Updating Exhibitors via Import
Once your initial exhibitor template has been imported, you can continue to edit and update your exhibitors via imports:
From your exhibitor list, click the 'Actions' drop-down.
Select 'Export Data' from the drop-down to export a .xlsx, .csv, or .xls file of your most up-to-date exhibitor information in the CMS.
Add any additional exhibitor info to the template.
Save your changes to the updated template and re-import in the CMS.
View ArticleSetting up attendee groups allows your attendees to filter the attendee list and search for attendees associated with a specific group.
You can set up groups based on roles, interests, or any other way you want to group attendees.
To set up attendee groups:
Go to the Content tab in the CMS and then click on your attendee list from the menu.
Click on the 'Attendee Groups' drop-down menu and then click 'Create New Attendee Group'.
Name the Attendee Group and click 'Create'.
Repeat the steps to create as many groups as you would like.
To associate an attendee with a particular group or groups:
Navigate to their profile in the attendee list and click into the box to highlight it blue.
Select the group(s) in the Attendee Groups drop-down menu, then click 'Apply'.
Note: you can select multiple attendees at once and apply groups at the same time.
View ArticleIf your event has a large number of sessions, you may want to consider adding Filters or Session Tracks to enable attendees to easily find sessions that are relevant to them.
Understanding and Using Session Tracks
Session Tracks are a way to create color-coded tracks in the agenda for different types of attendees to see agenda content relevant to them. For example, you can have tracks set up to indicate which sessions are available to different types of conference pass holders, or you can have tracks set up by attendee role to indicate which sessionsthey should attend.
To set up Session Tracks:
Go to the Content tab and then click on 'Agenda' in the menu.
Then click on theSession Tracksdrop-down menu and select 'Create New Session Track'.
Name your track and choose a color, and click 'Create'. You can have as many tracks as you would like.
To associate an agenda item with one or more Session Tracks, navigate to that agenda item and click on the Session Tracksbox. Check all of thetracksthat item should be associated with and click 'Apply'.
Understanding and Using Filters
Filters can be used to allow attendees to search for content of a specific type, such as "workshop", "keynote", or "happy hour".
To set up Filters:
Go to the Content tab and then click on 'Agenda' in the menu.
Then click on the Filters drop-down menu and select 'Create New Filter Group'. This will be the overarching group that the actual filters will be housed under.
Name your filter group and click 'Create'. For example, you might set up a filter group called "Activities" and then filters of "Golf Outings", "Dinners", and "Happy Hours".
Once you have the filter group created, you can click on the group name from the Filters dropdown and then click on 'Create new filter' to add as many filters under that group name as you would like.
Note: all filter groups and filters must have unique names.
To associate an agenda item or items with one or more filters:
Click on the agenda boxes to highlight them in blue, then click on the Filters dropdown and select the filter group.
Then select the box(es) next to the correct filter(s). Check all of the filters that item should be associated with and then click 'Apply'.
View ArticleDepending on the type of event that you're hosting, you may wish to assign attendees to a specific set of sessions. To do this in the DoubleDutch app, you will utilize the Personal Agenda feature.
Personal Agenda Options
Option 1:if you would like to assign attendees to some sessions, but still allow attendees to see the full agenda and add additional sessions to their personal agenda for further customization, then you will want to set 'Enable My Agenda' in the Setup tab of the CMS. This way, attendees can view the full agenda in the app and also view the sessions that you assign (through the process outlined below) under the "My Agenda" tab of the Agenda section.
here
Option 2:if you wish to prevent attendees from seeing the full agenda, and allow them to only see what they've been assigned by you for their personal agenda, please contact DoubleDutch Customer Support for additional internal app configurations in addition to following the process below to assign them sessions.
Setting Up Personal Agendas
Sessions that you assign through the process outlined below will appear under the "My Agenda" tab of the Agenda section in the app. Attendees will be reminded of upcoming sessions to which you've assigned them through our Personalized Cards.
Once you have loaded all of your agenda sessions into the CMS, you can assign sessions to attendees one at a time, or during a bulk import.
Assigning Sessions to One Attendee at a Time
Navigate to their attendee profile in the CMS.
Click on 'View personal agenda and bookmarked items'.
In the "Add an Item" box, starttyping inthe name of a session you want to add to this attendee's agenda. When the full name appears, click to add it.
Repeat Step 3 for all of the sessions you wish to add to this attendee's agenda.
To delete a session that was added in error or that you no longer wish this person to attend, click on the name of the session to highlight it in blue, and then click 'Remove Selected'.
Once you're done assigning sessions to this attendee, click 'Return to user details' above their name, and click on 'Save Changes'.
Assigning Sessions to Attendees as Part of a Bulk Import
Download the Attendee Import Template by clicking on 'Attendees' from the Content tab, and then click on 'Add Attendees', and select 'Download import template'.
In addition to the required fields necessary for import for each attendee row, in column R, you will list all of the session IDs (separated by a comma) that you want to be assigned for each attendee.To get the list of session IDs, click on your Agenda section in the Content tab and select 'Export Data' from the Actions drop-down. The unique ID for each item appears in Column J.
Note: please be sure to only list each uniquesession ID one time per attendeein the template,or you will get an error message that says you have "duplicate identifiers" when you try to upload the import template.
For more info on filling out the attendee import template, click .
Updating Personal Agendas via Bulk Import
Once your attendees' personal agendas have been added to the CMS, you can continue to edit them one at a time via the attendee's profile in the CMS, or you can bulk edit the personal agendas of all your attendees.
To edit via the import template, in your Attendees section:
Click the 'Actions' drop-down.
Select 'Export Attendees' from the drop-down to export a .xlsx, .csv, or .xls file of your most up-to-date attendee information in the CMS.
Add/remove session unique IDs in the Personal Agenda column of the template. You will need to listalldesired sessions in the attendees' personal agendas as the importer supports "de-linking" (meaning it will remove all sessions from the attendee's profile in the CMS that are not listed in the import template).
Save your changes to the updated attendee template and reimport your attendee template.
Notes
If you list a session more than once in the same attendee's personal agenda, you will receive a "duplicate identifier" error on the Summary page. Once you remove the duplicated session ID, you can import your template.
Changes to attendee personal agendas should update in the app after 20-30 minutes.
View ArticleWithin your event app, youmay wish to link to other content in your app. For example, you may want to include a link to a list of files in the description of a speaker profile, or you may want to set up the scanning of a QR code to unlock hidden content in the app.
Creating Links Using DD URLs
When you create the hyperlink, you'll need to enter the URL of the part of the app you want to open.
Note: these URLs are only functional within the app, either as a direct link or via the QR scanner.
Using the list below, determine the dd:// link you need.
Activity Feed
dd://activityfeed/
Display the Activity Feed
Agenda
dd://agenda/listID
Display an 'Agenda' list
Bookmarks
dd://favorites
Display the current user's bookmarks
Connections
dd://friends
Display the current user's connections
Files List
dd://topicinfo/listID
Display a 'Files and External Links' list
Hashtag
dd://hashtag/hashtagword
Display the #hashtag activity feed
Item Details
dd://item/itemID
Display the details view for a specific item
Leaderboard
dd://leaderboard/
Display the Leaderboard
List
dd://topic/listID
Display a list (any non-agenda type list such as a Speaker, Exhibitor, Sponsor, or Custom list)
Map
dd://map/
Display the Interactive Map
Meetings
dd://meetings/
Display the user's meetings
Poll
dd://poll/pollID
Display a Poll
Profile
dd://profile/userID
Display an attendee's profile
QR Code Scanner
dd://qrcodescanner
Display the QR code scanner
Surveys Section
dd://survey/
Display the Surveys section
Surveys
dd://survey/surveyID
Display a Survey
Users
dd://users/
Display the Attendee list
Topic Channel List
dd://channels
Display the Topic Channels list view
Topic Channel
dd://channels/channelroomID
Display a specific Topic Channel
Extensions
dd://extensions/extensionname
Display a specific Extension; for example, Live Q&A would be dd://extensions/questionanswer
Note:DD URLs do not work with Web Views.
If the type of URL you need requires an ID number at the end, you'll need to get that ID from the CMS:
Navigate to the exact item, list, poll, or survey, you want to link to.
Look at the URL of your CMS to determine the ID you need.
Individual Item (e.g. Speaker Profile)
You will need the number that follows /items/ in the URL.
link generator website
List (e.g. Exhibitor List)
You will need the number that follows /items/ in the URL.
Poll or Survey
You will need the number that follows /polls/ or /surveys/ in the URL.
If you are going to be creating a lot of dd:// URLs that require item IDs, you can get a list of all of your item IDs via an exportable report from the CMS. Otherwise, skip to step 7.
Navigate to the Event Performance section.
Click on the tab for Exportable Reports.
Download the ContentList report under the Content Engagementsection. The item IDs for all of the items in the app will be in column A in the report.
Combine the DD URL format from the table above and your ID from the CMS. To link to the speaker profile referenced in Step 2, your full URL will be dd://item/8773683
To create the link in the CMS, your setup should look like this (make sure Protocol is set to <other>):
Click 'OK'.
Creating Links Using the Link Generator
Additionally, you can create links to open in different ways in the app using DoubleDutch's link generator. These different ways are as follows:
Default Web View: opens the web page within the event app.
External Browser: opens the web page with the phone's default browser app (e.g. Safari, Chrome).
Native App: attempts to open the web page in a native application (e.g. Instagram, Twitter). If the native app is not supported, a default Web View will be used.
Javascript SDK:Opens a web page specialized for developers to create custom content. Provides basic integration hooks for receiving event information and customizing some UI.
From the, just enter the original URL you'd like to link to in the app, choose the method for how you would like to open in the app, and then click 'Generate'.
Note: when inputting the original URL, you must enter the full web address (https://).
View ArticleWhat is Attendee Session Tracking?
Attendee Session Tracking uses the badge scanning capability of the app to allow you to equip your event team to scan attendee badges as attendees enter the room for your agenda sessions. Now you'll be able to know exactly who came to each session and when they arrived!
Once an attendee is scanned into a session, they are then "checked in" to that session (the session will be bookmarkedon the attendee profile in the CMS), triggering other applicable logicin the appsuch as the Survey Reminder Card.
Since each scan is time-stamped, you can also use this feature if you're interested in tracking when attendees leave sessions by just scanning everyone on their way out.
Setting Up Attendee Session Tracking
To fully set this up for your event, there are some internal configurations that need to be enabled by DoubleDutch:
Please reach out to your DoubleDutch representative about using this feature.
DoubleDutch willalso need to work with you to make sure the badges you are using are configured to work with the scanner (see The Badge Setup section of the article for an idea of how that part works).
Next, you'll need to identify who on your team will be scanning badges and give them access to do so.
In the CMS, navigate toyour attendee list and click on the name of the individual you wish to give access to.
Click thecheckbox for "allow this attendee to scan for sessions".
Click 'Save Changes'.
Scanning Badges
When thatindividual isready to scan badges, they will navigate to the agenda details session in the app that you've assigned them to scan badges for.
There will be a "Scan Attendees" button that will appear. Tapping that button will open up the scanner and then they can point the device at the badge and it will register the attendee as checked in.
Viewing Attendee Session Tracking Reporting
In the CMS, you can access two different reports related to Attendee Session Tracking.Navigate to the Event Performance tab and then click on 'Exportable Reports'. In the "Attendee Session Tracking" section you will see the following reports:
Attendees Scanned Report: for each row, you will see the attendee's first and last name, email address, title, and company, as well as the scanner's first and last name. You will also see the session that the attendee attended and the timestamp of the scan. The last column will show the raw data scanned from the badge.
Scanners Report: for each row, you will see the scanner's first and last name, as well as their email address. You will see the session name for the session that they scanned for, the session start and end time, and the total number of badges they scanned. The next column shows the number of unique attendees scanned by that individual, and the final column shows the number of scans that the scanner was unable to associate with an attendee in the CMS.
View ArticleContent Visibility permissions allows you to easily segment your attendee groups to manage multi-group events and maintain control over sensitive content.In larger meetings or events, event organizers need to control what information (often sensitive) is distributed to which segments of attendees. Groups like VIPs, executives, speakers, and exhibitors require access to different information, such as special session or happy hour details for VIPs, sensitive strategy and decision making content for executives, and booth resources for exhibitors.
Content Visibility permissions allow event organizers to easily create and manage in-app content visibility rules in the CMS. Organizers can create multiple attendee groups and determine which list-type content is visible in each section of the app to each group. Sensitive information is now secure and only visible to the right groups.
Note: to enable Content Visibility for one of your events, please reach out to your DoubleDutch representative.
Creating Content Tiers Manually
To get started creating a tier in the CMS, first create a "General" tier.All content uploaded is automatically placed in the "Default" tier, which should not be used. Because of this, a "General" tier needs to be created. To create this:
Click on the "Content" tab, then click on the 'Tiers' button.
Custom Lists
Click 'Add Tier'
Type in "General" and click 'Save Changes'.
Assign all Attendees, Agenda, Speaker, Exhibitor, and Custom List content in the CMS to this new General tier. See below for how to assign content to tiers.
Repeat these steps to create your additional tiers.
Creating Content Tiers via Import
With Content Visibility enabled, the import spreadsheet templates for Attendees, Agendas, Speakers, Exhibitors and Custom Lists will include a column called "Tier Name". The Attendee template field will only accept one value (attendees can only be a part of one tier). The other templates will accept multiple values separated by commas (e.g. "tier1,tier2,tier3,testtier,staff,executives,general"). Importing these templates will create a tier in the CMS for every tier listed in that column.
Assigning Content to Tiers
There are two ways to assign content to tiers:
Using the import method mentioned above.
Manually adding content from the Attendees, Agenda, Speaker, Exhibitor, and Custom List content sections. Under each of those sections, you'll see a new drop-down menu titled "Tier". As you select content items, you can then click on the "Tiers" drop-down and select the checkboxes of where you would like to assign the content to. Then click 'Apply'.
Content Visibility Permissions FAQ
What type of content is supported?
Content Visibility permissions apply to only the followingfourapp sections: Agenda Sessions, Speakers, Exhibitors, and .
Can app sections be hidden?
App sections themselves cannotbe hidden; only the items within those app sections can be hidden. For example, everyone will be able to see the "Agenda" app section, but you can hide specific sessions from certain individuals, such as a "Roadmap" session that is only meant for customers.
Can "Files & Links" be hidden?
As noted above, the"Files and Links" app section is not among the four supported, though a Custom List app section could be created as a workaround, and include links that are hidden or visible across audience segments. While files can't be directly added to a Custom List, they can be added as links. They can also be added directly to agenda items.
Can "Folders" be hidden?
Folders cannot be hidden, so if you have a Custom List with folders, everyone will see the Custom List app section, as well as any folders. The best practice here is to ensure that if you have folders, that there is some content for everyone in each folder. If not, attendees without visibility permissions will see an empty folder.
One tierof attendees does not have visibility into any content in a specific section of the app.What should I do?
In the instance that a tier cannot see any content in a given section of the app, we recommend the following:
Create a new item in this section.
Title the section.
In the description of this item, type in an explanation of why this audience does not have access to this content.
Assign this item to the Tier.
Click 'Save'.
View ArticleMy Info allows you to curate content for specific attendees, attendee groups, or tiers. The content you "assign" will be reflected in what those individuals then see in the app.
For instance, if you'd like to have an attendee or group of attendees have visibility into information relevant only to them, you can do this with My Info.
Creating Custom Content
To enable My Info, go to the Discover More section in the CMS and click the 'Install Now' buttonon the corresponding box. You will then have a new section called "My Info" within your event.
Adding Content Cards
To add new content for attendees, click 'Add New Card'.
Attendee Groups
There are five content types you can select from:
Web Page
Plain Text
Survey
HTML
Video
A Web Page content type allows you to add a website that your selected attendees will have access to view in the app. Make sure you include the entire URL when inputting it in the "Add Content" field.
Note: Android doesn't support the opening of web pages that link to PDFs, images, or audio.
Plain Text content allows you to add text without HTML formatting.
You can encourage certain attendees to take one of your global surveys by choosing the Survey content type. All global surveys that you have created in the Surveys section of the app will appear as an option for you to add as a card.
Or you can add an Advanced Survey by posting the unique URL of the survey in the corresponding text field.
TheHTML content type allows you to add additional formatting beyond plain text. With HTML, you can display your content with text styling and images.
Add video from YouTube by selecting the Video option.The video must be a public-facing or unlisted YouTube URL.
Importing Content
Instead of creating multiple cards showing different info to several attendees, you also have the option to create one card with different info visible to individual attendees. This can be done using the import function on the Web Page, Plain Text, and Video content types. To explain this further using the Plain Text content type as an example:
Without Importing
Card Title
Info (Plain Text)
Attendees
Hotel Information for John
FOUND:RE Phoenix Hotel
1100 North Central Ave.
Phoenix, AZ 85003
Room #111
Hotel Information for Jane
FOUND:RE Phoenix Hotel
1100 North Central Ave.
Phoenix, AZ 85003
Room #301
With Importing
Card Title
Info (Plain Text)
Attendees
Hotel Information
FOUND:RE Phoenix Hotel
1100 North Central Ave.
Phoenix, AZ 85003
Room #111
FOUND:RE Phoenix Hotel
1100 North Central Ave.
Phoenix, AZ 85003
Room #301
To import your content, select the appropriate content type, then select 'Yes' under "Would you like to import individualized content from a CSV?".
An option to download the import template will appear. Select 'Download a CSV Template'. Fill out the spreadsheet and then, under "Choose file for Import", select and upload your completed file.
Selecting Attendees
Next, under the Attendees section, click the checkboxes next to the attendee names to give them visibility to that content type.
To make things easier, you can also use the search bar to find an attendee.
You can also select groups of attendees by clicking on 'Tiers'. Tiers are created using our Content Visibility feature.
And you can also click on 'Groups' to select a collection of attendees. Groups are determined by your in your attendee list.
Note: you cannot select individuals within tiers or groups unless you choose them from the "all attendees" list. When selecting tiers or groups, you can only select the full tier or the full group.
When you're finished creating your content type, click 'Close'. You can also remove a card at any time by clicking 'Delete'.
Reordering and Publishing Content
Once you have all of your content created, you can view the list of cards under the "Current Cards" box. The way the content appears in this section is the way it will appear for attendees in the app, as long as they have access to it.
However, you can change the order of the content by clicking on 'Reorder Cards'. Drag and drop the content types in the order you'd like and then click 'Save Order' when finished.
To publish a card, click 'Publish'. You will know the card is published as it will say "Live". You can also remove cards from being viewable in the app at any time by clicking 'Unpublish'.
Viewing Which Attendees Have Access to Which Content
To view what content will look like to certain attendees, click 'View Attendees' at the bottom of the main My Info page. This will expand the attendee list. Click on an attendee name to see what content they have access to in the phone mockup on the right side of the screen.
View ArticleTopics can be imported into the CMS using the import templates found in each content section (Sessions, Speakers, Exhibitors, etc.). In the template, there will be a column labeled "Topics". In the Topics field, list the topics associated with each item, comma-separated. Apostrophes cannot be included in this field.
here
Once uploaded, your items will be tagged with the Topics in the CMS.
Learn about Topic Tagging Best Practices .
View ArticleWhat is Topic Tagging?
Topic tagging allows you to assign topics to sessions when creating the agenda in your event app. After the event, you can pull the data to see a wealth of information about attendees:
Session attendance
Bookmarked sessions and topics
Participation in conversations about sessions, topics, speakers and more
Whether you are hosting an external event or internal event, that data is a goldmine for marketers, sales, HR, and other teams alike (more to come on that topic soon), but for now, let's discuss how to get started topic tagging sessions at your events. The strategy you use will have a big impact on the quality of data you're able to collect during the event and the value that data will have after the event.
Set Your Tagging Strategy By Working Backwards
The goal with topic tagging is to capture relevant, structured data post-event. So, the natural first step is to identify how you will use this information. A few questions to ask yourself:
For marketers:
What are key areas of interest that indicate a prospect is high value or ready to buy?
How does your marketing team segment, identify, and prioritize prospects?
What engagement data about prospects would be valuable to your sales team?
For internal meeting organizers:
What are key topic areas you want your employees to be aligned on?
What information about attendance do you need to track certifications and training requirements?
What education metrics do you want to be able to report on to your executive team?
Be Clear and Consistent
Make sure your topic tags are clear so that anyone who looks at the post-event data can understand what they're looking at. And if you run several events, use a similar strategy across all of them so you can compare the data across events.
Avoid Too Many (and Too Few) Topic Tags
Using too many topic tags means you're getting too specific. Too few tags, meanwhile, means you may not be able to learn anything valuable after the event. In general, you can ensure your final data set is more manageable by consolidating multiple sessions under the same tag.
There is no golden rule to determine the ideal number of topics you should create for your event, but topic numbers should generally scale with your event. A multi-day user conference with thousands of sessions and multiple tracks, such as Dreamforce, will obviously have a larger set of topic tags than a one-day sales kickoff with three tracks and 15 sessions.
Remember Why You're Tagging In the First Place
The most important thing to keep in mind when you start to use topic tagging is that data is the ultimate goal. You want to be able to track your audience's behaviors and interests to give you and other teams within your company valuable targeting, education, segmentation, and account management information. This powerful capability can be used in so many ways throughout your company, and just a little bit of strategy upfront can pay big dividends long after the closing session.
Learn how to set up Topic Tags here.
View ArticleWhat is Networking?
Goal Definition: I want my attendees to foster and expand their networks.
Relevant Event Types: Sales Kickoff, Incentive and Rewards Trip, Corporate Internal Meeting, Training or Seminar, Roadshow, User or Partner Conference, Financial Services Client Event, Conference, Medical or Scientific Conference, Expo or Tradeshow, Executive Summit, Customer Advisory Board
How do I increase Networking?
To maximize networking at your event, and to collect data around who and what your attendees are interested in connecting with, enable the following features:
Show the Attendee List:Make sure the attendee list is visible and near the top of your app menu so everyone can see who’s at the event.
Create Topic Channels:Create dedicated channels for the topics your attendees are interested in. Attendees can join channels and participate in the conversation with others who share similar interests. You can also have a speaker or team member moderate the channel, adding questions to spark the conversation. Here are a few ideas for Channel topics: First Time Attendees; Veteran Attendees; Meet our Product Team; Industry Trends; Department Segments; Attendee Regions or Run Club.
Promote Session Channels:Like Topic Channels, Session Channels are a dedicated space for attendees to have an open forum during a session. It’s a great way to crowdsource questions for the speaker and share key session learnings while engaging with other attendees participating in the same session.
Enable Direct Messaging:When direct messaging is enabled, attendees can chat directly with other attendees- whether they meet at breakfast, in a session or through a topic or session channel.
Promote @Mentioning within the Activity Feed:Create a promoted post letting attendees know that they can communicate andconnect with other attendees by @mentioning them within the activity feed.
Attendee Meetings:The meeting scheduling feature allows attendees to request meetings with otherattendees through in-app calendar invites.
Leaderboard:Create a leaderboard challenge to encourage attendees to engage within theapp. The app automatically assigns points to actions within the app. Attendees who are engaging the most will appear on the leaderboard. This can create a friendly competition among your attendees and drive networking.
Email Digests:There are multiple digest emails that are automatically sent to attendeesduring and after the event. They are designed to drive attendees back into the app throughout the event. These emails include top app posts, suggested attendees to follow, and general news happening in the app.
Following Attendees:Let other attendees know they can follow others within the app to stay up to date on what others are saying throughout the event with a promoted post or live from a keynote speaker. When attendees select to follow other attendees, the app will automatically suggest similar people to follow.
Want to learn more about setting and measuring event goals? Click here to learn how DoubleDutch features and Event Performance measurements can be used to drive business outcomes!
View ArticleBelow is a summary of current issues currently faced by customers releasing apps in China.
Google App Store
There is no access to the Google Play Store in China. Because of this, DoubleDutch is not responsible for hosting the app in China. You will receive a .apkhandoff file, and it is recommended that you either host the file on your eventwebpage, or a suitable China app store (Baidu, Tencent, 360, Wendoujia, etc.)
Interactive Maps
Interactive Maps won’t work without Google Play Services; they will result in an error message. It is possible to side-load Google Play Services but attendees willnot do this. The short-term option is to create web-based maps for users without Google Play Services. The downside with this is there is no offline mode and map labels are visible.
PDF Viewer
PDFs currently openin a Google Docs web view for some versions of the app (Android doesn’t support PDFs well out of the box, compared to iOS. However, in China, Google Docs is blocked. The proposed solution is to convert thedocument from PDF to HTML.
Push Notifications
Push Notifications will not work without Google Play Services. Instead, any messages sent by the organizer will be received as in-app notifications.
Xiaomi (Other Chinese) Device Compatibility
Issues may vary with phones from other Chinese manufacturers. There are numerous brands and Android models out there, so there's no guaranteethe app will function properly.
View ArticleBelow are the most common issues and errors you may encounter during the app distribution process.
App Transfer
Issue
Solution
Team ID & Account Holder Email invalid when initiating an app transfer
Please see the following instructions:
Log in to Apple Developer
Click on the "Membership" tab
Copy the alphanumeric digits next to Team ID
Right-click on the Account Holder name and copy the email address
Send both items to DoubleDutch
Receive a warning message for a “Potential loss of Keychain access” when uploading the .ipa file to App Store Connect.
This is just a warning message that should cause no concern. It’s just letting you know that the app is changing from our account to yours. Click next and complete.The Developer will also get an email about the potential loss of keychain access.
Push Notification Certificates
Issue
Solution
Unable to export the push cert as a .p12 file type
Ensure that you are exporting from the “My Certificates” section in your keychain. If you try to export from another section, it will be greyed out.
Re-codesigning
If you receive any of the following error messages while re-codesigning in Terminal:
Issue
Solution
“You have 0 valid signing identities. A valid Distribution Certificate is needed to continue.”
There was a step missed when configuring the distribution cert. Please walk through the steps and then try again.
Right-click the distribution file in keychain. Choose 'get info'. There will be a triangle next to the words "trust" and "details". Select 'trust' and make sure each value is set to trust and then try again.
“Time of codesigning not correct. Codesigning was not successful.”
Confirm that you are using the most recent recodesign.sh script. If you downloaded it to your device previously, please re-download the latest one then try again.
“Signature date is not recognized. Please take a screenshot and contact customer support. Invalid Signature date."
Go into Keychain Access and delete both of the Distribution Certificates.Go to the Apple Developer portal and download the latest Distribution Certificate. Make sure to double-click and install this after downloading.Go to the Provisioning Profile in the Apple Developer portal, click edit for the one that’s associated with your app, and make sure the date matches the provisioning profile. If not, select the correct date.
"This provisioning profile does not have Associated Domains entitlement!"
You do not have your App ID setup properly for Associated Domains. You will need to fix this before signing again. Please see the following instructions:
Login in to your developer account. Navigate to "Identifiers", then "App ID's", Click on the specific App ID and then 'Enable Associated Domains'.
Then go to "Provisioning Profiles", then "Distribution". Select the provisioning profile to edit, then generate a provisioning profile.
Re-try the re-codesign process.
“Invalid provisioning profile. This app contains an embedded provisioning profile that is not associated with Team ID _____.”
Deleted the Distribution Certificate and Provisioning Profile that was initially created and recreate them.
"Invalid argument as it is of file type: inode/x-empty."
This means the DoubleDutch .ipa file isn’t there anymore. Ensure that you have uploaded the .ipa file from the zip file you received from DoubleDutch.
App Store Connect
Issue
Solution
In App Store Connect, you received the following error when trying to upload the app: “Redundant Binary Upload”
An app was already uploaded and is still processing. It’s possible to see what builds are processing by selecting "Activity" while viewing your app in App Store Connect.
Rejection notice from Apple:
We identified one or more issues with a recent delivery for your app, ______. Please correct the following issues, then upload again.
"Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.”
This means someone re-codesigned with “-e” for enterprise when they shouldn’t have.
View ArticleOrganizing Your App Files
DoubleDutch recommends that you keep a folder on your desktop titled something like "App Files" or "DoubleDutch App Files", or the name of your app, with the following files:
Provisioning Profile
Re-Codesign Script
Most recent build of your .ipa file
Push Notification Certificate (P12)
Emailing App Files
If you are going to email the binary files to colleagues for processing or review, please do so after you have zipped the binary. We have seen in the past that email servers can corrupt the binary files if sent in an unzipped state. This happens usually because of the built-in virus scanners. Microsoft’s Exchange Server is an example.
Whitelisting Connections
To enable proper data flow between the app client and the relevant database, it may be necessary to whitelist the connections in your corporate firewall to the API:
api.doubledutch.me
api.eu.doubledutch.me
us-identity.doubledutch.me
eu-identity.doubledutch.me
It depends on where your app’s database is hosted. Ask your DoubleDutch representative for this information if it is necessary.
Wrapping With Toolkits
DoubleDutch does not support the use of toolkits for wrapping the app. For instance, the use of the MDX Toolkit with Citrix’s XenMobile. The various toolkits that exist in the market have proven difficult to debug in the past and have caused too great of a risk to proper app functionality. This is why we chose not to support them. If you choose to use a toolkit anyway, it is at your own risk and we cannot be responsible for the incorrect functioning of the app afterward.
If you still choose to wrap the app in a toolkit, it is important to note that the app needs permission to connect to the following services on the iOS device:
Push Notifications
Location
Background App Refresh
Photos
Calendar Access
Secure Server for In-House Apps
The server where the iOS app is to be hosted for download must be secured with SSL.
View ArticleWith Enterprise Distribution, your app will be distributed internally using a mobile app management system, which will only be used by employees or authorized partners/participants.
Distributing your App through Enterprise Distribution
Most likely you have a Mobile Device Management (MDM) system such as MobileIron, Airwatch, or XenMobile by Citrix. These platforms are used to manage corporate devices used by employees and to distribute apps to those devices.
It is highly advised to have a technical resource ready to carry out the necessary steps in order to deploy the app successfully.
Once the image assets and other app info have been submitted in the CMS, the app creation request will be sent to the DoubleDutch App Opps team. Then the app will be built and all relevant binary and image files will be sent to you in ZIP files by your DoubleDutch representative.
Next, follow the steps below to complete the publishing process via Enterprise Distribution for iOS:
Step 1: Getting Started with Apple Developer
In order to start the process of publishing your iOS app to the App Store, someone in your organization will need to enroll in Apple's Developer Program. Once your organization enrolls in the Developer Program, you will then have a Developer Account.
To enroll in Apple's Developer Program, follow the steps at:
https://developer.apple.com/programs/
IMPORTANT: make sure you enroll as an Organization, NOT as an Individual.
For more information on enrolling in Apple's Developer Program, click here.
Once you have a Developer Account, the person who enrolled will be considered the account holder and has the capability to grant users access and delegate responsibilities.
Step 2: How to Create an App ID
The second step to complete and publish your app is to create a unique App ID in your Apple Developer account.Creating an App ID is necessary in order to register, upload, and distribute an app.
Follow the steps below to create your App ID:
Navigate to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
re-codesign package
Click on the Identifiers section in the left menu. Above the list and to the right of the Identifiers title, you will see a “+” sign. Click this to create a new App ID.
On the next screen, click the radio button next to App IDs. Then click 'Continue'.
Now you will see a form that needs to be filled in to register a new App ID:
Make sure the "iOS, tvOS, watchOS" radio button is selected.
Type the name of the app in the Description field. Be specific and avoid generic terms because all app names in iTunes have to be unique. Also, confirm your Team ID.
Now you will need to fill in a unique Bundle ID for this App ID.A Bundle ID is typically a reverse URL or domain name of your organization, coupled with the app name. This is done in order to create a truly unique identifier for your app. (e.g. com.companydomain.appname)
The services your app supports and that should be enabled are: Associated Domains, Game Center, In-App Purchase, and most importantly Push Notifications. Apple has determined that Game Center and In-App Purchase are to be mandatory for all apps. The last service will enable you to send Push Notifications to attendees from the CMS. Then, click 'Continue'.
You will be taken to an overview to check the data you have entered. If it is correct, click on 'Register'.
Step 3: How to Create a Push Notification Certificate
A Push Notification Certificate is necessary in order to send push notifications to attendees via your app. In order to create a Push Notification Certificate, follow the steps below.
Navigate to Apple Developer and log in.
Click on 'Certificates, Identifiers & Profiles'.
Select 'Identifiers', locate your app, and click on the name.
Scroll down the page to "Push Notifications" and click 'Configure'.
A pop-up window will appear. Click on 'Create Certificate' underProduction SSL Certificate.
Click 'Learn More' under "Upload a Certificate Signing Request" to learn how to create a Certificate Signing Request (CSR) file. Then go back to Apple Developer and click 'Choose File'.
Use Finder to find your CSR file, select it, and click on 'Open' in the dialog window. It will now be visible in the browser. Click on 'Continue'; it will take a moment to show the next window.
Click on 'Continue'; it may take a moment to show the next window.
Your certificate is ready for download. Click on 'Download'.
Locate the downloaded file, called “aps.cer”, on your Mac and click on it. It will trigger Keychain Access to open.
To find the certificate in Keychain Access, you can use the Search field in the top-right of the dialog window. Type in the Bundle ID of the App ID. You can now confirm that the Push Certificate was correctly created, is valid, and has an associated private key.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_pushcert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system. You will be notified when you can test Push Notifications on your app.
Note: Push Notification Certificates expire after 12 months. You will receive an email from Apple when that occurs; please let your DoubleDutch representative know when your certificate expires. At that time you will create a new Push Notification Certificate by following the process mentioned above. Also,you will need a Mac computer in order to create your push notification certificate or else push messages won't work.
Step 4: How to Create a Distribution Certificate
A Distribution Certificate identifies your organization within a distribution provisioning profile and allows you to submit your app to the store.
IMPORTANT: you will only need to create one Distribution Certificate for your Developer Account, even if you have multiple apps.
To create a Distribution Certificate:
Log in to Apple Developer.
Click on 'Certificates, Identifiers & Profiles'.
The next screen should default to the "Certificates" section.
Click on the '+' button to add a new certificate.
Select 'iOS Distribution (App Store and Ad Hoc)' from the Software options, then click 'Continue'.
Click 'Continue' again.
Click 'Choose File' and select the CSR file youpreviously created. Then click 'Continue'.
Click the 'Download' button to download a .cerfile.
Double-click the .cer file to install it in Keychain Access.
If you encounter any issues during the app distribution process, a DoubleDutch representative may ask you to send a P12 version of your distribution certificate. Here are the steps to create the P12 file:
Go to Keychain Access, and search for the distribution certificate.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_distrocert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, another dialog will open; input your computer password and click 'Allow'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system.
Note: sending your Distribution Certificate to DoubleDutch is completely optional and only necessary in cases where you have asked DoubleDutch to troubleshoot app distribution issues. Also, Distribution Certificates expire after 12 months. You will receive an email from Apple when that occurs. At that time you will create a new Distribution Certificate by following the process mentioned above.
Step 5: How to Create a Provisioning Profile
Provisioning Profiles are needed to define how and to which devices your app will be distributed. Without a Provisioning Profile, you cannot distribute an app through the App Store, or through your own internal distribution method.
Go to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
Click on the 'Profiles' section. Then click on the '+' next to the "Profiles" title.
Select the radio button next to “App Store” underneath the Distribution heading. This is the Provisioning Profile needed in order to be able to upload your app to App Store Connect.Then click on the 'Continue' button at the top.
Note: if you are publishing your app via Enterprise Distribution you will select "In House" instead of "App Store".
Next, you will be asked to select an App ID with which to associate this Provisioning Profile. Click on the drop-down list and select the App ID that belongs to your app.Then click the 'Continue' button.
Next, you will be asked to select the Distribution Certificate that this Provisioning Profile will be linked to. Most likely, you will have only one. Select that certificate by clicking on the radio button next to it.Then click 'Continue'.
The final step is to give this Provisioning Profile a name. It is best to give it the same name as your app. You can also include today’s date, to document the date of creation. Then click on 'Generate'.
You can then download the generated Provisioning Profile and save it to your desktop.
Step 6: How to Re-Codesign Your App
When distributing your iOS app inside your organization via a Mobile Device Management system (MDM) you will have to re-codesign the binary file (.ipa).
Downloading the Re-Codesign Package
In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.
Go to https://bit.ly/ddrecodesign
Download the re-codesign package file.
Find the ZIP file on your Mac and double-click on it.
It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.
Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.
Prerequisites for Successful Re-Codesigning
A Mac computer.
Transporter installed on the Mac. If you don't have Transporter downloaded you can download it here.
Xcode 10.1 or higher installed on the Mac. If you don't have Xcode downloaded you can download it here.
Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
The, provided by DoubleDutch.
The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.
Re-Codesigning your iOS App
Open the “codesign” folder where you have the recodesign.sh script and theTerminal window.
Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file.For Enterprise apps, type in "-e" after the script file path.
Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
Finally, drag & drop the .ipa file you received into the Terminal window.
You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
Then hit the 'Enter/Return' key. An example of the Terminal output is shown below:
When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.
Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
You can close the open windows and proceed to upload your app to your organization's mobile app management system.
Final Technical Notes on Re-Codesigning
This app claims two specific entitlements: Apple's Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.
Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
If Push Notifications are not available in the Provisioning Profile, the script will output the message: "This provisioning profile doesn't have push entitlement!"
Keychain Access is necessary to store the user's login and password combination so that the user can access the app, after closing and reopening, without re-logging in.
Next, you will upload the app binary to your MDM.
Finally, send your Push Notification Certificate (P12) to DoubleDutch.
Note: it is important to remember that the Apple Mac computer that is performing this has the Enterprise Distribution Certificate installed in the Keychain Access app. It must also have a different name than your organization’s public iPhone Distribution Certificate. The re-codesign tool requires that Distribution Certificates have unique names.
For Android Enterprise Apps, you will simply receive an .apk file and use that to upload to your MDM.
View ArticleIf you're submitting your app for the first time under your developer account (after DoubleDutch has transferred the app to you), follow the steps below to complete the update process.
Note: click on the name of each step to view the process.
Step 1: How to Create a Push Notification Certificate
A Push Notification Certificate is necessary in order to send push notifications to attendees via your app. In order to create a Push Notification Certificate, follow the steps below.
Navigate to Apple Developer and log in.
Click on 'Certificates, Identifiers & Profiles'.
App Store Connect
Select 'Identifiers', locate your app, and click on the name.
Scroll down the page to "Push Notifications" and click 'Configure'.
A pop-up window will appear. Click on 'Create Certificate' underProduction SSL Certificate.
Click 'Learn More' under "Upload a Certificate Signing Request" to learn how to create a Certificate Signing Request (CSR) file. Then go back to Apple Developer and click 'Choose File'.
Use Finder to find your CSR file, select it, and click on 'Open' in the dialog window. It will now be visible in the browser. Click on 'Continue'; it will take a moment to show the next window.
Click on 'Continue'; it may take a moment to show the next window.
Your certificate is ready for download. Click on 'Download'.
Locate the downloaded file, called “aps.cer”, on your Mac and click on it. It will trigger Keychain Access to open.
To find the certificate in Keychain Access, you can use the Search field in the top-right of the dialog window. Type in the Bundle ID of the App ID. You can now confirm that the Push Certificate was correctly created, is valid, and has an associated private key.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_pushcert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system. You will be notified when you can test Push Notifications on your app.
Note: Push Notification Certificates expire after 12 months. You will receive an email from Apple when that occurs; please let your DoubleDutch representative know when your certificate expires. At that time you will create a new Push Notification Certificate by following the process mentioned above. Also,you will need a Mac computer in order to create your push notification certificate or else push messages won't work.
Step 2: How to Create a Distribution Certificate
A Distribution Certificate identifies your organization within a distribution provisioning profile and allows you to submit your app to the store.
IMPORTANT: you will only need to create one Distribution Certificate for your Developer Account, even if you have multiple apps.
To create a Distribution Certificate:
Log in to Apple Developer.
Click on 'Certificates, Identifiers & Profiles'.
The next screen should default to the "Certificates" section.
Click on the '+' button to add a new certificate.
Select 'iOS Distribution (App Store and Ad Hoc)' from the Software options, then click 'Continue'.
Click 'Continue' again.
Click 'Choose File' and select the CSR file youpreviously created. Then click 'Continue'.
Click the 'Download' button to download a .cerfile.
Double-click the .cer file to install it in Keychain Access.
If you encounter any issues during the app distribution process, a DoubleDutch representative may ask you to send a P12 version of your distribution certificate. Here are the steps to create the P12 file:
Go to Keychain Access, and search for the distribution certificate.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_distrocert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, another dialog will open; input your computer password and click 'Allow'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system.
Note: sending your Distribution Certificate to DoubleDutch is completely optional and only necessary in cases where you have asked DoubleDutch to troubleshoot app distribution issues. Also, Distribution Certificates expire after 12 months. You will receive an email from Apple when that occurs. At that time you will create a new Distribution Certificate by following the process mentioned above.
Step 3: How to Create a Provisioning Profile
Provisioning Profiles are needed to define how and to which devices your app will be distributed. Without a Provisioning Profile, you cannot distribute an app through the App Store, or through your own internal distribution method.
Go to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
Click on the 'Profiles' section. Then click on the '+' next to the "Profiles" title.
Select the radio button next to “App Store” underneath the Distribution heading. This is the Provisioning Profile needed in order to be able to upload your app to App Store Connect.Then click on the 'Continue' button at the top.
Note: if you are publishing your app via Enterprise Distribution you will select "In House" instead of "App Store".
Next, you will be asked to select an App ID with which to associate this Provisioning Profile. Click on the drop-down list and select the App ID that belongs to your app.Then click the 'Continue' button.
Next, you will be asked to select the Distribution Certificate that this Provisioning Profile will be linked to. Most likely, you will have only one. Select that certificate by clicking on the radio button next to it.Then click 'Continue'.
The final step is to give this Provisioning Profile a name. It is best to give it the same name as your app. You can also include today’s date, to document the date of creation. Then click on 'Generate'.
You can then download the generated Provisioning Profile and save it to your desktop.
Step 4: How to Re-Codesign Your App
When distributing your iOS app through your own iTunes account you will have to re-codesign the binary file (.ipa).
Downloading the Re-Codesign Package
In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.
Go to https://bit.ly/ddrecodesign
Download the re-codesign package file.
Find the ZIP file on your Mac and double-click on it.
It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.
Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.
Prerequisites for Successful Re-Codesigning
A Mac computer.
Transporter installed on the Mac. If you don't have Transporter downloaded you can download it here.
Xcode 10.1 or higher installed on the Mac. If you don't have Xcode downloaded you can download it here.
Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
The re-codesign package, provided by DoubleDutch.
The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.
Re-Codesigning your iOS App
Open the “codesign” folder where you have the recodesign.sh script and theTerminal window.
Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file.
Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
Finally, drag & drop the .ipa file you received into the Terminal window.
You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
Then hit the 'Enter/Return' key. An example of the Terminal output is shown below:
When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.
Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
You can close the open windows and proceed to upload your app to your App Store Connect account.
Final Technical Notes on Re-Codesigning
This app claims two specific entitlements: Apple's Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.
Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
If Push Notifications are not available in the Provisioning Profile, the script will output the message: "This provisioning profile doesn't have push entitlement!"
Keychain Access is necessary to store the user's login and password combination so that the user can access the app, after closing and reopening, without re-logging in.
Step 5: Uploading your App to App Store Connect
After you have re-codesigned your iOS app, you should be able to upload the binary file to your App Store Connect account. If you are uploading the app to your internal app store, see the administrator of your Mobile Application Management System.
You can upload your app to App Store Connect by using the Transporter app on your Mac.
Follow the steps below to upload your app successfully to your App Store Connect account.
Find the Transporter app on your Mac. You can open Spotlight search and type in “transporter”. It will be the top hit.
Open the app and log into the app with the credentials you use to log into App Store Connect. Apple may ask you to create an app-specific password during this step. You can find the directions on how to create an app-specific password here.
Drag the .ipa file you re-codesigned, from the Codesign_Output folder on your Desktop, to the "Add App" screen of Transporter.
Then you will see an overview of the app’s details. Click on 'Deliver' to proceed with uploading.
The upload process will take a few minutes. Afterward, you can close Transporter.
Step 6: How to Fill in an App Store Connect App Listing
Log in to.
Next, click on the 'My Apps' button to go to the overview of your apps.
If you don’t have many apps, you should be able to spot your app immediately. Click on it once to be taken to the app listing. If you have many apps, you can use the Search field to find your app.
Once you have opened your app’s listing, in the left menu click on the '+' sign next to “Version or Platform”. It will show you another window where you can select iOS or tvOS. Select iOS.
Then another window will pop up where you will need to enter the new version number of your app. Use logical numeric order. If your current app is version 1.0, the version you will type in is 1.1. If you had version 1.9 in the App Store, your next version would be 2.0. Then click 'Create'.
Then you will see the new app listing. All the fields are the same as when you first filled in the app listing, except the new field at the top where you can specify what the changes are in this new version. To keep it concise, you can type in “Bug Fixes and Feature Enhancements”.
If you have any changes to make to the images, remember to delete the old ones before submitting the app for review. If you need to change the app icon, you must first delete the old one, only then can you upload a new one to the app listing.If desired, you can also change the app name at this time. This can be done by selecting "App Information" in the upper left-hand corner of the app listing in App Store Connect.
All other fields can remain the same unless specified by DoubleDutch that changes have been made. After every change you make to the app listing, it is prudent to click on the 'Save' button in the top-right.
The final step will be to select a new build to associate with this updated app listing. The new .ipa file you uploaded earlier should be available to select by this point in the “Build” section of the app listing. You will see a “+” sign next to the heading. Click on it to open a pop-up window.
If you do not see the “+” sign, it means that your app is still being processed by Apple’s servers. It should become available within 30 minutes of uploading. You can periodically refresh the app listing page by pressing: CMD + R.
Note: due to Apple’s web security settings on App Store Connect, it may happen that your session will be closed when you refresh the page. Do not worry; you will be taken back to the login page. Simply log in again, find your app and continue your work where you left off. This is also a reason why it is prudentto save your work frequently.
The pop-up window should show your app build, ready to be selected. Click on the radio button next to the build number and then click on 'Done'.
You will be taken back to the main app listing page, click on 'Save' in the top-right.
Once your new app listing is saved, with all new images, icon, name, description, and new app build attached to the listing, you can click on 'Submit for Review' in the top right.
The final stage to confirm your submission is to answer two questions about Export Compliance and an Advertising Identifier in the app. You can select 'No' for both of the questions, then click on 'Submit'.
You will now be taken back to the app listing, and as a confirmation, you will see that your app has the status “Waiting for Review”.
You have finished your app update! This means that your app submission has been put into the review queue in Apple’s review department. Typically, reviews of app updates take less time than new apps. However, it all depends on Apple and their review queue. App update approval can take as long as up to two weeks. It is advisable to take this into account when planning your app launch.
View ArticleAs of May 1st, 2018, DoubleDutch is no longer able to update customers' iOS apps in our own DoubleDutch developer account. To read more about this change, please view this article from the DoubleDutch Blog.
Because of Apple's new rules, and if DoubleDutch has been updating your app for you, you will need to make sure that your company hasan Apple Developer account so you can update your iOS app on your own. The process for creating an Apple Developer account can be found here.
Before the transfer process can be initiated you will need to send the following to your DoubleDutch representative:
Apple ID (the email address of the account holder)
Team ID (under the Membership section in App Store Connect)
To locate your Team ID, please see the instructions here.
Transferring an App
When you're ready to have your app transferred to your account, your DoubleDutch representative will work with you to facilitate a transfer of your app(s) from the DoubleDutch developer account to the account of your company. To accept a transfer, please follow the steps from Apple's support article. Keep in mind that app transfers can only be accepted by the Account Holder role in your developer account.
You will also need the following information in order to complete the transfer process:
Privacy Policy URL: https://doubledutch.me/privacy
Support URL: https://attendeesupport.doubledutch.me
Marketing URL: https://doubledutch.me/product/event-app/
App Review contact information (your company, NOT DoubleDutch)
App Store contact information (your company, NOT DoubleDutch)
App transfers will take approximately two business days to take effect. You can find more information about the app transfer process at the App Store Connect Developer Help site.
Note: you must also go into your Apple Developer account and change the Demo Account from the DoubleDutch email address to an email address associated with your organization. Failure to do this will result in app update rejections by Apple. Instructions to complete this can be found under step 21 of How to Fill in an App Store Connect App Listing.
The transferred app file will be the most up-to-date; the app is now live and available in the store with your Apple developer account.
As updates to the app become available, DoubleDutch will send you app update files as needed so you can update your app in App Store Connect. Before you can begin making updates, you will need to complete the steps in the article here.
Note: you will need a Mac computer in order to complete the rest of the app transfer process. Please make sure you create a P12 (Push Notification Certificate) as soon as possible and send to your DoubleDutch representative. Otherwise, Push Notifications will not work!
View ArticleAfter you have re-codesigned your iOS app, you should be able to upload the binary file to your App Store Connect account. If you are uploading the app to your internal app store, see the administrator of your Mobile Application Management System.
You can upload your app to App Store Connect by using the Transporter app on your Mac.
Follow the steps below to upload your app successfully to your App Store Connect account.
Find the Transporter app on your Mac. You can open Spotlight search and type in “transporter”. It will be the top hit.
Open the app and log into the app with the credentials you use to log into App Store Connect. Apple may ask you to create an app-specific password during this step. You can find the directions on how to create an app-specific password here.
Updating an Existing App under your Apple Developer Account
Drag the .ipa file you re-codesigned, from the Codesign_Output folder on your Desktop, to the "Add App" screen of Transporter.
Then you will see an overview of the app’s details. Click on 'Deliver' to proceed with uploading.
The upload process will take a few minutes. Afterward, you can close Transporter.
If you are publishing your app for the first time, go back to the How to Fill in an App Store Connect App Listing step, and continue from step 16.
If you are updating an existing app, go to
View ArticleThe steps below will show you how to successfully fill in an app listing in App Store Connect and submit your app for review for the first time.
Log in to App Store Connect.
Next, click on the 'My Apps' button to go to the overview of your apps.
here
Since this is the first time you will be uploading and publishing your app, a new app listing needs to be created. Click on the '+' sign in the top-left of the window and choose to create a 'New App'.
After that, a new window will pop up and ask you for several details about your new app listing.
Select the iOS check box.
Enter a unique name into the "Name" field. If you enter a name that has already been used in the App Store or registered by another developer, the name field will turn red and give an error.
Choose a primary language for your app listing.
Choose the Bundle ID you created earlier for this app, you can click on the drop-down menu and find your Bundle ID in the list.
Finally, enter an SKU this is meant as a "code identifier", however, it is not really important for publishing. Simply entering the App Name in all capitals, followed by a number is sufficient.
Then click on 'Create'.
Your app listing should be created now and you will be taken to the App Information section. You will see your app name and Bundle ID, your app's newly created and assigned Apple ID number and a few fields on the right that need filling in.
The privacy policy URL should be the DoubleDutch privacy policy. This can be found here: http://doubledutch.me/privacy/
The Category of your app falls under the “Productivity” category.
After making these changes, click on 'Save' in the top-right of the window to save your work before going to the next section.
Next, click on 'Pricing and Availability' in the left menu.
Here you will select the 'zero' price for your app and the countries your app will be available in. By default, your app will be available in all countries.
This is normal and fine. If you choose to limit the availability of your app to your country, this is at your own risk for the adoption of your app and the support response time by DoubleDutch.
Note: it is strongly advised to leave the USA, Netherlands, and the Philippines checked in the availability list so that DoubleDutch can provide support swiftly if needed. These are the countries we operate out of.
You can safely ignore the “Volume Purchase Program” section, seeing as your app is being offered for free.
Click on 'Save' in the top-right to save your work.
Then navigate to the “Prepare for Submission” section in the menu, here you will upload images, the icon, and fill in the app description.
First, you can upload the splash screen images and screenshots of your app into the screenshot area. You can drag and drop the images into the field. As you can see above the field, there are tabs for iPhone and iPad.
Each device requires at least two images and of certain dimensions. See the Annex below for a list of the dimension requirements of each device. Drag the two images into the field, then click on the next device tab to do the same for that device. When you are finished, click on 'Save' to save your work before continuing to the next section.
Note: screenshots are provided by DoubleDutch in the link containing the IPA file.
Next, you can fill in the "Description" field. The text you enter here will be visible as the app’s description in the App Store. Beware; there are some limitations to this field.
Next, to the description field, you can see the Keywords, Support URL, and Marketing URL. In the "Keywords" field, you can enter the app name and event name as default terms. The Support URL is the link to where users can find support for the app, which is https://attendeesupport.doubledutch.me. The Marketing URL is the marketing description of the app, which is http://doubledutch.me/product/event-app/.
Continue to the next step in the distribution process: Uploading your App to App Store Connect, then come back to this page to complete the rest of the steps.
The next section is the "Build" section where you can select the app build to attach to this app listing. This is the re-codesigned IPA you created during the re-codesigning process.
Click on the '+' sign next to the heading, under "Build", and select your build in the window that pops up.
Note:it can take up to 15 minutes for the "+" sign to appear after uploading your app build.
Click on 'Save' in the top-right to save your work.
Next, you can drag and drop your app icon image into the App Icon field.
Note: the App Icon must have dimensions of 1024 x 1024 pixels!
Next to the app icon section, you can see the Copyright and Trade Representative section. The copyright belongs to DoubleDutch, Inc. The Trade Representative Contact Information can be filled in with the contact information of your organization where your Apple Developer has been registered as residing.
Afterward, the app needs a Rating. You can see the rating section underneath the App Icon section. By default, when you first create the app listing, the app has no rating. You have to answer several questions in order to determine the rating of your app. Click on 'Edit' to open up a window with the questions.
Note: These are the default answers given about apps published by DoubleDutch. If your app will contain any information about alcohol, tobacco, drug use, gambling, or medical topics, please adjust the rating.
Next, you can fill in the App Review Information. Here you can enter the contact information of the person responsible for the Apple Developer account within your organization. Typically, it is the person that has been given the Account Holder role in your organization. All fields are required to be filled.
Below that, there is a Demo Account field. This is the user account that Apple Reviewers will use to log into the app and check its functionality and viability for the App Store. Input an email address from your organization here and then make sure that you add the email as an attendee in the CMS for your events.
Next, you can enter something into the Notes field. Best practice is to enter a secondary contact in case the App Reviewer needs more information to approve the app. Include information like a telephone number and email address. This field is not visible in the app listing in the App Store.
Finally, you can determine when the app will be released into the App Store. Typically, it is best to leave it on the default setting “Automatically release this version” so that your app is available as soon as possible. If for some reason you would like to have your app only available from a certain date, you can choose this. However, please discuss the implications of this with your DoubleDutch representative.
Note: it takes at least one day for the app to visible in all countries after beingreleased into the App Store. It can happen that after ‘going live’ the app will beseen immediately in the USA, but it will take several hours for it to be visiblein the App Store in the Netherlands. This is something to consider whenplanning a specific date for app release.
Click on 'Save' to finalize your work and continue to app submission.
After you have saved your work, the button to “Submit for Review” should be colored in and ready to be clicked. Click on it. You will be taken to another page with three final questions about your app. The following are the default answers for your app:
Export Compliance No
Content Rights No
Advertising Identifier (IDFA) - No
Click on 'Submit'. You will be taken back to your app listing now and the status should have changed to “Waiting for Review”.
You're finished!
Note: it can take about 2-10 days for your app to be reviewed, please plan accordingly with your DoubleDutch representative.
Annex -iOS Device Screenshot Dimensions
The dimensions below are the required screenshots for an app listing, the other iOS device specific screenshots have become optional.
The dimensions below are in pixels width by height.
iPhone X - 1125 x 2436
iPhone 6 4.7 inch 750 x 1334
iPhone 6 Plus 5.5 inch 1242 x 2208
iPhone 5 4 inch 640 x 1136
iPhone 4 3.5 inch 640 x 960
iPad 768 x 1024
iPad Pro 12.9 inch 2048 x 2732
For a detailed guide on screenshot dimension requirements, you can view Apple’s documentation .
View ArticleApp Store Connect is used to submit and manage your app. After you've created an Apple Developer account, you can use the same credentials to log in to App Store Connect.
How to Fill in an App Store Connect App Listing
Once you've logged into App Store Connect, you should see a screen that looks similar to the one below.
If at any time you have any questions about App Store Connect, please refer to Apple's App Store Connect Guide.
In the meantime, continue to the next step in the distribution process: .
View ArticleA Push Notification Certificate is necessary in order to send push notifications to attendees via your app. In order to create a Push Notification Certificate, follow the steps below.
Navigate to Apple Developer and log in.
Click on 'Certificates, Identifiers & Profiles'.
How to Create a Distribution Certificate
Select 'Identifiers', locate your app, and click on the name.
Scroll down the page to "Push Notifications" and click 'Configure'.
A pop-up window will appear. Click on 'Create Certificate' underProduction SSL Certificate.
Click 'Learn More' under "Upload a Certificate Signing Request" to learn how to create a Certificate Signing Request (CSR) file. Then go back to Apple Developer and click 'Choose File'.
Use Finder to find your CSR file, select it, and click on 'Open' in the dialog window. It will now be visible in the browser. Click on 'Continue'; it will take a moment to show the next window.
Click on 'Continue'; it may take a moment to show the next window.
Your certificate is ready for download. Click on 'Download'.
Locate the downloaded file, called “aps.cer”, on your Mac and click on it. It will trigger Keychain Access to open.
To find the certificate in Keychain Access, you can use the Search field in the top-right of the dialog window. Type in the Bundle ID of the App ID. You can now confirm that the Push Certificate was correctly created, is valid, and has an associated private key.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_pushcert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system. You will be notified when you can test Push Notifications on your app.
Note: Push Notification Certificates expire after 12 months. You will receive an email from Apple when that occurs; please let your DoubleDutch representative know when your certificate expires. At that time you will create a new Push Notification Certificate by following the process mentioned above. Also,you will need a Mac computer in order to create your push notification certificate or else push messages won't work.
Continue to the next step in the distribution process: .
View ArticleIf there has been an upgrade or change made to your app, DoubleDutch will supply you with a new build of your app. It will have a higher version number, bug fixes, and/or possibly some feature enhancements. What you will want to do is upload it to App Store Connect and have it approved by Apple as soon as possible so that your users can benefit from the upgrade. Below are the steps to update your app.
Note: click on the name of each step to view the process.
Step 1: How to Re-Codesign your App
When distributing your iOS app through your own iTunes account you will have to re-codesign the binary file (.ipa).
Downloading the Re-Codesign Package
In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.
Go to https://bit.ly/ddrecodesign
Download the re-codesign package file.
Find the ZIP file on your Mac and double-click on it.
It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.
Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.
Prerequisites for Successful Re-Codesigning
A Mac computer.
Transporter installed on the Mac. If you don't have Transporter downloaded you can download it here.
Xcode 10.1 or higher installed on the Mac. If you don't have Xcode downloaded you can download it here.
Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
The re-codesign package, provided by DoubleDutch.
The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.
Re-Codesigning your iOS App
Open the “codesign” folder where you have the recodesign.sh script and theTerminal window.
Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file.
Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
Finally, drag & drop the .ipa file you received into the Terminal window.
You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
App Store Connect
Then hit the 'Enter/Return' key. An example of the Terminal output is shown below:
When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.
Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
You can close the open windows and proceed to upload your app to your App Store Connect account.
Final Technical Notes on Re-Codesigning
This app claims two specific entitlements: Apple's Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.
Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
If Push Notifications are not available in the Provisioning Profile, the script will output the message: "This provisioning profile doesn't have push entitlement!"
Keychain Access is necessary to store the user's login and password combination so that the user can access the app, after closing and reopening, without re-logging in.
Step 2: Uploading your App to App Store Connect
After you have re-codesigned your iOS app, you should be able to upload the binary file to your App Store Connect account. If you are uploading the app to your internal app store, see the administrator of your Mobile Application Management System.
You can upload your app to App Store Connect by using the Transporter app on your Mac.
Follow the steps below to upload your app successfully to your App Store Connect account.
Find the Transporter app on your Mac. You can open Spotlight search and type in “transporter”. It will be the top hit.
Open the app and log into the app with the credentials you use to log into App Store Connect. Apple may ask you to create an app-specific password during this step. You can find the directions on how to create an app-specific password here.
Drag the .ipa file you re-codesigned, from the Codesign_Output folder on your Desktop, to the "Add App" screen of Transporter.
Then you will see an overview of the app’s details. Click on 'Deliver' to proceed with uploading.
The upload process will take a few minutes. Afterward, you can close Transporter.
Step 3: How to Fill in an App Store Connect App Listing
Log in to.
Next, click on the 'My Apps' button to go to the overview of your apps.
If you don’t have many apps, you should be able to spot your app immediately. Click on it once to be taken to the app listing. If you have many apps, you can use the Search field to find your app.
Once you have opened your app’s listing, in the left menu click on the '+' sign next to “Version or Platform”. It will show you another window where you can select iOS or tvOS. Select iOS.
Then another window will pop up where you will need to enter the new version number of your app. Use logical numeric order. If your current app is version 1.0, the version you will type in is 1.1. If you had version 1.9 in the App Store, your next version would be 2.0. Then click 'Create'.
Then you will see the new app listing. All the fields are the same as when you first filled in the app listing, except the new field at the top where you can specify what the changes are in this new version. To keep it concise, you can type in “Bug Fixes and Feature Enhancements”.
If you have any changes to make to the images, remember to delete the old ones before submitting the app for review. If you need to change the app icon, you must first delete the old one, only then can you upload a new one to the app listing. If desired, you can also change the app name at this time.
All other fields can remain the same unless specified by DoubleDutch that changes have been made. After every change you make to the app listing, it is prudent to click on the 'Save' button in the top-right.
The final step will be to select a new build to associate with this updated app listing. The new .ipa file you uploaded earlier should be available to select by this point in the “Build” section of the app listing. You will see a “+” sign next to the heading. Click on it to open a pop-up window.
If you do not see the “+” sign, it means that your app is still being processed by Apple’s servers. It should become available within 30 minutes of uploading. You can periodically refresh the app listing page by pressing: CMD + R.
Note: due to Apple’s web security settings on App Store Connect, it may happen that your session will be closed when you refresh the page. Do not worry; you will be taken back to the login page. Simply log in again, find your app and continue your work where you left off. This is also a reason why it is prudentto save your work frequently.
The pop-up window should show your app build, ready to be selected. Click on the radio button next to the build number and then click on 'Done'.
You will be taken back to the main app listing page, click on 'Save' in the top-right.
Once your new app listing is saved, with all new images, icon, name, description, and new app build attached to the listing, you can click on 'Submit for Review' in the top right.
The final stage to confirm your submission is to answer two questions about Export Compliance and an Advertising Identifier in the app. You can select 'No' for both of the questions, then click on 'Submit'.
You will now be taken back to the app listing, and as a confirmation, you will see that your app has the status “Waiting for Review”.
You have finished your app update! This means that your app submission has been put into the review queue in Apple’s review department. Typically, reviews of app updates take less time than new apps. However, it all depends on Apple and their review queue. App update approval can take as long as up to two weeks. It is advisable to take this into account when planning your app launch.
View ArticleWith Client Distribution for iOS, your app will be distributed in the public Apple App Store. This is the most common way to distribute your app.
To get started, first, complete the app creation process in the CMS. DoubleDutch will build the app for you with placeholder certificates and bundle names. Your DoubleDutch representative will send you all the relevant image files and the app binaries in ZIP files.
Then follow the steps below.
WARNING: you must have a Mac computer in order to complete the full iOS app distribution process!
Note: click on the name of each step to view the process.
Step 1: Getting Started with Apple Developer
In order to start the process of publishing your iOS app to the App Store, someone in your organization will need to enroll in Apple's Developer Program. Once your organization enrolls in the Developer Program, you will then have a Developer Account.
To enroll in Apple's Developer Program, follow the steps at:
https://developer.apple.com/programs/
IMPORTANT: make sure you enroll as an Organization, NOT as an Individual.
For more information on enrolling in Apple's Developer Program, click here.
Once you have a Developer Account, the person who enrolled will be considered the account holder and has the capability to grant users access and delegate responsibilities.
Note: enrollment in Apple's Developer Program costs $99 annually.
Step 2: How to Create an App ID
The second step to complete and publish your app is to create a unique App ID in your Apple Developer account.Creating an App ID is necessary in order to register, upload, and distribute an app.
Follow the steps below to create your App ID:
Navigate to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
here
Click on the Identifiers section in the left menu. Above the list and to the right of the Identifiers title, you will see a “+” sign. Click this to create a new App ID.
On the next screen, click the radio button next to App IDs. Then click 'Continue'.
Now you will see a form that needs to be filled in to register a new App ID:
Make sure the "iOS, tvOS, watchOS" radio button is selected.
Type the name of the app in the Description field. Be specific and avoid generic terms because all app names in iTunes have to be unique. Also, confirm your Team ID.
Now you will need to fill in a unique Bundle ID for this App ID.A Bundle ID is typically a reverse URL or domain name of your organization, coupled with the app name. This is done in order to create a truly unique identifier for your app. (e.g. com.companydomain.appname)
The services your app supports and that should be enabled are: Associated Domains, Game Center, In-App Purchase, and most importantly Push Notifications. Apple has determined that Game Center and In-App Purchase are to be mandatory for all apps. The last service will enable you to send Push Notifications to attendees from the CMS. Then, click 'Continue'.
You will be taken to an overview to check the data you have entered. If it is correct, click on 'Register'.
Step 3: How to Create a Push Notification Certificate
A Push Notification Certificate is necessary in order to send push notifications to attendees via your app. In order to create a Push Notification Certificate, follow the steps below.
Navigate to Apple Developer and log in.
Click on 'Certificates, Identifiers & Profiles'.
Select 'Identifiers', locate your app, and click on the name.
Scroll down the page to "Push Notifications" and click 'Configure'.
A pop-up window will appear. Click on 'Create Certificate' underProduction SSL Certificate.
Click 'Learn More' under "Upload a Certificate Signing Request" to learn how to create a Certificate Signing Request (CSR) file. Then go back to Apple Developer and click 'Choose File'.
Use Finder to find your CSR file, select it, and click on 'Open' in the dialog window. It will now be visible in the browser. Click on 'Continue'; it will take a moment to show the next window.
Click on 'Continue'; it may take a moment to show the next window.
Your certificate is ready for download. Click on 'Download'.
Locate the downloaded file, called “aps.cer”, on your Mac and click on it. It will trigger Keychain Access to open.
To find the certificate in Keychain Access, you can use the Search field in the top-right of the dialog window. Type in the Bundle ID of the App ID. You can now confirm that the Push Certificate was correctly created, is valid, and has an associated private key.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_pushcert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system. You will be notified when you can test Push Notifications on your app.
Note: Push Notification Certificates expire after 12 months. You will receive an email from Apple when that occurs; please let your DoubleDutch representative know when your certificate expires. At that time you will create a new Push Notification Certificate by following the process mentioned above. Also,you will need a Mac computer in order to create your push notification certificate or else push messages won't work.
Step 4: How to Create a Distribution Certificate
A Distribution Certificate identifies your organization within a distribution provisioning profile and allows you to submit your app to the store.
IMPORTANT: you will only need to create one Distribution Certificate for your Developer Account, even if you have multiple apps.
To create a Distribution Certificate:
Log in to Apple Developer.
Click on 'Certificates, Identifiers & Profiles'.
The next screen should default to the "Certificates" section.
Click on the '+' button to add a new certificate.
Select 'iOS Distribution (App Store and Ad Hoc)' from the Software options, then click 'Continue'.
Click 'Continue' again.
Click 'Choose File' and select the CSR file youpreviously created. Then click 'Continue'.
Click the 'Download' button to download a .cerfile.
Double-click the .cer file to install it in Keychain Access.
If you encounter any issues during the app distribution process, a DoubleDutch representative may ask you to send a P12 version of your distribution certificate. Here are the steps to create the P12 file:
Go to Keychain Access, and search for the distribution certificate.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_distrocert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, another dialog will open; input your computer password and click 'Allow'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system.
Note: sending your Distribution Certificate to DoubleDutch is completely optional and only necessary in cases where you have asked DoubleDutch to troubleshoot app distribution issues. Also, Distribution Certificates expire after 12 months. You will receive an email from Apple when that occurs. At that time you will create a new Distribution Certificate by following the process mentioned above.
Step 5: How to Create a Provisioning Profile
Provisioning Profiles are needed to define how and to which devices your app will be distributed. Without a Provisioning Profile, you cannot distribute an app through the App Store, or through your own internal distribution method.
Go to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
Click on the 'Profiles' section. Then click on the '+' next to the "Profiles" title.
Select the radio button next to “App Store” underneath the Distribution heading. This is the Provisioning Profile needed in order to be able to upload your app to App Store Connect.Then click on the 'Continue' button at the top.
Note: if you are publishing your app via Enterprise Distribution you will select "In House" instead of "App Store".
Next, you will be asked to select an App ID with which to associate this Provisioning Profile. Click on the drop-down list and select the App ID that belongs to your app.Then click the 'Continue' button.
Next, you will be asked to select the Distribution Certificate that this Provisioning Profile will be linked to. Most likely, you will have only one. Select that certificate by clicking on the radio button next to it.Then click 'Continue'.
The final step is to give this Provisioning Profile a name. It is best to give it the same name as your app. You can also include today’s date, to document the date of creation. Then click on 'Generate'.
You can then download the generated Provisioning Profile and save it to your desktop.
Step 6: How to Re-Codesign your App
When distributing your iOS app through your own iTunes account you will have to re-codesign the binary file (.ipa).
Downloading the Re-Codesign Package
In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.
Go to https://bit.ly/ddrecodesign
Download the re-codesign package file.
Find the ZIP file on your Mac and double-click on it.
It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.
Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.
Prerequisites for Successful Re-Codesigning
A Mac computer.
Transporter installed on the Mac. If you don't have Transporter downloaded you can download it here.
Xcode 10.1 or higher installed on the Mac. If you don't have Xcode downloaded you can download it here.
Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
The re-codesign package, provided by DoubleDutch.
The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.
Re-Codesigning your iOS App
Open the “codesign” folder where you have the recodesign.sh script and theTerminal window.
Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file.
Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
Finally, drag & drop the .ipa file you received into the Terminal window.
You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
Then hit the 'Enter/Return' key. An example of the Terminal output is shown below:
When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.
Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
You can close the open windows and proceed to upload your app to your App Store Connect account.
Final Technical Notes on Re-Codesigning
This app claims two specific entitlements: Apple's Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.
Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
If Push Notifications are not available in the Provisioning Profile, the script will output the message: "This provisioning profile doesn't have push entitlement!"
Keychain Access is necessary to store the user's login and password combination so that the user can access the app, after closing and reopening, without re-logging in.
Step 7: Getting Started with App Store Connect
App Store Connect is used to submit and manage your app. After you've created an Apple Developer account, you can use the same credentials to log in to App Store Connect.
Once you've logged in to App Store Connect, you should see a screen that looks similar to the one below.
If at any time you have any questions about App Store Connect, please refer to Apple's App Store Connect Guide.
Step 8: How to Fill in an App Store Connect App Listing
The steps below will show you how to successfully fill in an app listing in App Store Connect and submit your app for review for the first time.
Log in to App Store Connect.
Next, click on the 'My Apps' button to go to the overview of your apps.
Since this is the first time you will be uploading and publishing your app, a new app listing needs to be created. Click on the '+' sign in the top-left of the window and choose to create a 'New App'.
After that, a new window will pop up and ask you for several details about your new app listing.
Select the iOS check box.
Enter a unique name into the "Name" field. If you enter a name that has already been used in the App Store or registered by another developer, the name field will turn red and give an error.
Choose a primary language for your app listing.
Choose the Bundle ID you created earlier for this app, you can click on the drop-down menu and find your Bundle ID in the list.
Finally, enter an SKU this is meant as a "code identifier", however, it is not really important for publishing. Simply entering the App Name in all capitals, followed by a number is sufficient.
Then click on 'Create'.
Your app listing should be created now and you will be taken to the App Information section. You will see your app name and Bundle ID, your app's newly created and assigned Apple ID number and a few fields on the right that need filling in.
The privacy policy URL should be the DoubleDutch privacy policy. This can be found here: http://doubledutch.me/privacy/
The Category of your app falls under the “Productivity” category.
After making these changes, click on 'Save' in the top-right of the window to save your work before going to the next section.
Next, click on 'Pricing and Availability' in the left menu.
Here you will select the 'zero' price for your app and the countries your app will be available in. By default, your app will be available in all countries.
This is normal and fine. If you choose to limit the availability of your app to your country, this is at your own risk for the adoption of your app and the support response time by DoubleDutch.
Note: it is strongly advised to leave the USA, Netherlands, and the Philippines checked in the availability list so that DoubleDutch can provide support swiftly if needed. These are the countries we operate out of.
You can safely ignore the “Volume Purchase Program” section, seeing as your app is being offered for free.
Click on 'Save' in the top-right to save your work.
Then navigate to the “Prepare for Submission” section in the menu, here you will upload images, the icon, and fill in the app description.
First, you can upload the splash screen images and screenshots of your app into the screenshot area. You can drag and drop the images into the field. As you can see above the field, there are tabs for iPhone and iPad.
Each device requires at least two images and of certain dimensions. See the Annex below for a list of the dimension requirements of each device. Drag the two images into the field, then click on the next device tab to do the same for that device. When you are finished, click on 'Save' to save your work before continuing to the next section.
Note: screenshots are provided by DoubleDutch in the link containing the IPA file.
Next, you can fill in the "Description" field. The text you enter here will be visible as the app’s description in the App Store. Beware; there are some limitations to this field.
Next, to the description field, you can see the Keywords, Support URL, and Marketing URL. In the "Keywords" field, you can enter the app name and event name as default terms. The Support URL is the link to where users can find support for the app, which is https://attendeesupport.doubledutch.me. The Marketing URL is the marketing description of the app, which is http://doubledutch.me/product/event-app/.
Continue to the next step in the distribution process: "Uploading your App to App Store Connect", then come back to this section to complete the rest of the steps.
The next section is the "Build" section where you can select the app build to attach to this app listing. This is the re-codesigned IPA you created during the re-codesigning process.
Click on the '+' sign next to the heading, under "Build", and select your build in the window that pops up.
Note:it can take up to 15 minutes for the "+" sign to appear after uploading your app build.
Click on 'Save' in the top-right to save your work.
Next, you can drag and drop your app icon image into the App Icon field.
Note: the App Icon must have dimensions of 1024 x 1024 pixels!
Next to the app icon section, you can see the Copyright and Trade Representative section. The copyright belongs to DoubleDutch, Inc. The Trade Representative Contact Information can be filled in with the contact information of your organization where your Apple Developer has been registered as residing.
Afterward, the app needs a Rating. You can see the rating section underneath the App Icon section. By default, when you first create the app listing, the app has no rating. You have to answer several questions in order to determine the rating of your app. Click on 'Edit' to open up a window with the questions.
Note: These are the default answers given about apps published by DoubleDutch. If your app will contain any information about alcohol, tobacco, drug use, gambling, or medical topics, please adjust the rating.
Next, you can fill in the App Review Information. Here you can enter the contact information of the person responsible for the Apple Developer account within your organization. Typically, it is the person that has been given the Account Holder role in your organization. All fields are required to be filled.
Below that, there is a Demo Account field. This is the user account that Apple Reviewers will use to log into the app and check its functionality and viability for the App Store. Input an email address from your organization here and then make sure that you add the email as an attendee in the CMS for your events.
Next, you can enter something into the Notes field. Best practice is to enter a secondary contact in case the App Reviewer needs more information to approve the app. Include information like a telephone number and email address. This field is not visible in the app listing in the App Store.
Finally, you can determine when the app will be released into the App Store. Typically, it is best to leave it on the default setting “Automatically release this version” so that your app is available as soon as possible. If for some reason you would like to have your app only available from a certain date, you can choose this. However, please discuss the implications of this with your DoubleDutch representative.
Note: it takes at least one day for the app to visible in all countries after beingreleased into the App Store. It can happen that after ‘going live’ the app will beseen immediately in the USA, but it will take several hours for it to be visiblein the App Store in the Netherlands. This is something to consider whenplanning a specific date for app release.
Click on 'Save' to finalize your work and continue to app submission.
After you have saved your work, the button to “Submit for Review” should be colored in and ready to be clicked. Click on it. You will be taken to another page with three final questions about your app. The following are the default answers for your app:
Export Compliance No
Content Rights No
Advertising Identifier (IDFA) - No
Click on 'Submit'. You will be taken back to your app listing now and the status should have changed to “Waiting for Review”.
You're finished!
Note: it can take about 2-10 days for your app to be reviewed, please plan accordingly with your DoubleDutch representative.
Annex -iOS Device Screenshot Dimensions
The dimensions below are the required screenshots for an app listing, the other iOS device specific screenshots have become optional.
The dimensions below are in pixels width by height.
iPhone X - 1125 x 2436
iPhone 6 4.7 inch 750 x 1334
iPhone 6 Plus 5.5 inch 1242 x 2208
iPhone 5 4 inch 640 x 1136
iPhone 4 3.5 inch 640 x 960
iPad 768 x 1024
iPad Pro 12.9 inch 2048 x 2732
For a detailed guide on screenshot dimension requirements, you can view Apple’s documentation here.
Step 9: Uploading your App to App Store Connect
After you have re-codesigned your iOS app, you should be able to upload the binary file to your App Store Connect account. If you are uploading the app to your internal app store, see the administrator of your Mobile Application Management System.
You can upload your app to App Store Connect by using the Transporter app on your Mac.
Follow the steps below to upload your app successfully to your App Store Connect account.
Find the Transporter app on your Mac. You can open Spotlight search and type in “transporter”. It will be the top hit.
Open the app and log into the app with the credentials you use to log into App Store Connect. Apple may ask you to create an app-specific password during this step. You can find the directions on how to create an app-specific password.
Drag the .ipa file you re-codesigned, from the Codesign_Output folder on your Desktop, to the "Add App" screen of Transporter.
Then you will see an overview of the app’s details. Click on 'Deliver' to proceed with uploading.
The upload process will take a few minutes. Afterward, you can close Transporter.
To complete the process, go back to the "How to Fill in an App Store Connect App Listing"process, and continue from step 16.
Note: any subsequent changes will need to be discussed with your DoubleDutch representative. For instance, if you revoke and renew a Push Notification Certificate.
View ArticleWhen distributing your iOS app through your own iTunes account or inside your organization via a Mobile Device Management system (MDM) you will have to re-codesign the binary file (.ipa).
Downloading the Re-Codesign Package
In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.
Go to https://bit.ly/ddrecodesign
Download the re-codesign package file.
Find the ZIP file on your Mac and double-click on it.
It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.
Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.
Prerequisites for Successful Re-Codesigning
A Mac computer.
Transporter installed on the Mac. If you don't have Transporter downloaded you can download it here.
Xcode 10.1 or higher installed on the Mac. If you don't have Xcode downloaded you can download it here.
Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
The re-codesign package, provided by DoubleDutch.
The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.
Re-Codesigning your iOS App
Open the “codesign” folder where you have the recodesign.sh script and theTerminal window.
Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file. For Enterprise apps, type in "-e" after the script file path.
Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
Finally, drag & drop the .ipa file you received into the Terminal window.
You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
Getting Started with App Store Connect
Then hit the 'Enter/Return' key. An example of the Terminal output is shown below:
When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.
Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
You can close the open windows and proceed to upload your app to your App Store Connect account or your organization's mobile app management system.
Continue to the next step in the distribution process:.
Final Technical Notes on Re-Codesigning
This app claims two specific entitlements: Apple's Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.
Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
If Push Notifications are not available in the Provisioning Profile, the script will output the message: "This provisioning profile doesn't have push entitlement!"
Keychain Access is necessary to store the user's login and password combination so that the user can access the app, after closing and reopening, without re-logging in.
View ArticleProvisioning Profiles are needed to define how and to which devices your app will be distributed. Without a Provisioning Profile, you cannot distribute an app through the App Store, or through your own internal distribution method.
Go to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
How to Re-Codesign Your App
Click on the 'Profiles' section. Then click on the '+' next to the "Profiles" title.
Select the radio button next to “App Store” underneath the Distribution heading. This is the Provisioning Profile needed in order to be able to upload your app to App Store Connect.Then click on the 'Continue' button at the top.
Note: if you are publishing your app via Enterprise Distribution you will select "In House" instead of "App Store".
Next, you will be asked to select an App ID with which to associate this Provisioning Profile. Click on the drop-down list and select the App ID that belongs to your app.Then click the 'Continue' button.
Next, you will be asked to select the Distribution Certificate that this Provisioning Profile will be linked to. Most likely, you will have only one. Select that certificate by clicking on the radio button next to it.Then click 'Continue'.
The final step is to give this Provisioning Profile a name. It is best to give it the same name as your app. You can also include today’s date, to document the date of creation. Then click on 'Generate'.
You can then download the generated Provisioning Profile and save it to your desktop.
Continue to the next step in the distribution process:.
View ArticleA Distribution Certificate identifies your organization within a distribution provisioning profile and allows you to submit your app to the store.
IMPORTANT: you will only need to create one Distribution Certificate for your Developer Account, even if you have multiple apps.
To create a Distribution Certificate:
Log in to Apple Developer.
Click on 'Certificates, Identifiers & Profiles'.
How to Create a Provisioning Profile
The next screen should default to the "Certificates" section.
Click on the '+' button to add a new certificate.
Select 'iOS Distribution (App Store and Ad Hoc)' from the Software options, then click 'Continue'.
Click 'Continue' again.
Click 'Choose File' and select the CSR file youpreviously created. Then click 'Continue'.
Click the 'Download' button to download a .cerfile.
Double-click the .cer file to install it in Keychain Access.
If you encounter any issues during the app distribution process, a DoubleDutch representative may ask you to send a P12 version of your distribution certificate. Here are the steps to create the P12 file:
Go to Keychain Access, and search for the distribution certificate.
Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: "Apple Push Services...”
A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_distrocert”. Then click 'Save'.
Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in "doubledutch2019" and enter it twice as requested. Click 'OK'.
Next, another dialog will open; input your computer password and click 'Allow'.
Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system.
Note: sending your Distribution Certificate to DoubleDutch is completely optional and only necessary in cases where you have asked DoubleDutch to troubleshoot app distribution issues. Also, Distribution Certificates expire after 12 months. You will receive an email from Apple when that occurs. At that time you will create a new Distribution Certificate by following the process mentioned above.
Continue to the next step in the distribution process:.
View ArticleThe second step to complete and publish your app is to create a unique App ID in your Apple Developer account.Creating an App ID is necessary in order to register, upload, and distribute an app.
Follow the steps below to create your App ID:
Navigate to Apple Developer and log in with your credentials.
Click on 'Certificates, Identifiers & Profiles'.
How to Create a Push Notification Certificate
Click on the Identifiers section in the left menu. Above the list and to the right of the Identifiers title, you will see a “+” sign. Click this to create a new App ID.
On the next screen, click the radio button next to App IDs. Then click 'Continue'.
Now you will see a form that needs to be filled in to register a new App ID:
Make sure the "iOS, tvOS, watchOS" radio button is selected.
Type the name of the app in the Description field. Be specific and avoid generic terms because all app names in iTunes have to be unique. Also, confirm your Team ID.
Now you will need to fill in a unique Bundle ID for this App ID.A Bundle ID is typically a reverse URL or domain name of your organization, coupled with the app name. This is done in order to create a truly unique identifier for your app. (e.g. com.companydomain.appname)
The services your app supports and that should be enabled are: Associated Domains, Game Center, In-App Purchase, and most importantly Push Notifications. Apple has determined that Game Center and In-App Purchase are to be mandatory for all apps. The last service will enable you to send Push Notifications to attendees from the CMS. Then, click 'Continue'.
You will be taken to an overview to check the data you have entered. If it is correct, click on 'Register'.
Continue to the next step in the iOS distribution process:.
View ArticleIn order to start the process of publishing your iOS app to the App Store, someone in your organization will need to enroll in Apple's Developer Program. Once your organization enrolls in the Developer Program, you will then have a Developer Account.
To enroll in Apple's Developer Program, follow the steps at:
https://developer.apple.com/programs/
IMPORTANT: make sure you enroll as an Organization, NOT as an Individual.
For more information on enrolling in Apple's Developer Program, click here.
Once you have a Developer Account, the person who enrolled will be considered the account holder and has the capability to grant users access and delegate responsibilities.
Note: enrollment in Apple's Developer Program costs $99 annually.
Continue to the next step in the iOS distribution process: How to Create an App ID.
View ArticleIf you have a well-known brand or if you are using (with appropriate permission) a well-known logo in the promotion, image assets or naming of your event or conference, you may run into issues with the Google Play Store.
To try to prevent issues, Google has created a method for contacting them in advance of your app submission to help prevent unnecessary issues, rejections or suspensions.
Click here toview a Google support article on app rejections and suspensions.
Click here to fill out the form and send the information to Google.
View ArticleTo publish an app in the Google Play Store you will need to create an app listing. The steps below will show you how to successfully fill in the app listing and submit your app for the first time.
Log into your Google Developer account.
Click on the button 'Create Application' in the top right.
Start by selecting the default language and filling in the app name in the popup window. Then click 'Create'.
Privacy Policy
Fill in the title (this is the app name that will be visible to users browsing the Play Store), short description, and the full description in the relevant fields.
Then upload the image assets to the relevant slots.
Scroll down and fill in the Categorization section. For Application Type, select 'Applications'. For Category, select 'Productivity'. We'll come back to the Content Rating after we upload the APK file.
Continue to scroll down and fill out the Contact Details and Privacy Policy. For the Privacy Policy, it's best to use theDoubleDutch .
Click 'Save Draft' to save your work.
Next, click on 'App Releases' in the left menu. Then click on 'Manage Production'.
Then click on 'Create Release'.
You will then be taken to a form to upload your APK file. Under the Google Play App Signing section, select 'Opt Out'. A pop-up will appear; click 'Confirm'.
Next, drag and drop the APK file you received from DoubleDutch into the "APKs to add" section. You'll notice that the release name will auto-populate.
Under "What's in this release?" it's recommended that you put "Bug Fixes and Feature Enhancements". Then, click 'Save'.
Next, click on 'Content Rating' in the left menu. There you will need to start a new questionnaire and fill in questions to determine the age rating of the app. Click 'Continue' to start the questionnaire. Then, input the email address you'd like to use for ratings related communications and select the App Category: Social Networking, Forums, and UGC Sharing.
Answers the questions on the next page by clicking the radio buttons, then click on 'Save Questionnaire', then 'Calculate Rating'.
Then the rating is shown on a new page. Scroll down and click on 'Apply Rating'.
Next, click on Pricing & Distribution in the left menu. The app’s price should be set as “Free”.
Also, make sure to have the app available in all countries. If you cannot, then make it available in the countries you wish and the Netherlands, USA, and Philippines these countries have our support teams who can help with issues when you report them. If you do not, our team will not be able to download the app and troubleshoot.
Then make click 'No' on the Primarily Child-Directed question and sure to click 'Yes' on the radio button to confirm that the app contains ads. The app offers the feature of Promoted Posts, which counts as in-app ads in Google’s criteria.
Scroll down in the Consent section, and check all the boxes.
Once all these fields are filled in, click 'Save Draft'.
After this, you should see four green check marks next to the following section names in the left menu: App Releases, Store Listing, Content Rating, and Pricing & Distribution. This means your app is ready to be published.
Click on 'App Releases' in the left menu. Then click 'Edit Release'. Then 'Review'. Review the release information on the next screen and then click on 'Start Rollout to Production' to submit your app for review.
You’re finished!
Note: it can take about several days for your app to be reviewed, please plan accordingly with your DoubleDutch representative.
View ArticleGoogle Play Developer Access Overview
Per Google’s Terms and Conditions, DoubleDutch is not permitted to host customers’ apps in its own Google Play Developer account. Instead, using the Release Manager role, DoubleDutch can gain access to your Google Play Developer account. It allows us to work autonomously and get Android apps published, updated, or fixed as fast as possible.
Note: this role does not allow for changing any fundamental account information. That permission is restricted to the Google account that was registered with the creation of the Google Play Developer account. If necessary, it is possible to grant Release Manager access to only the app or apps created and managed by DoubleDutch. Also, this permission level is given to one functional account within DoubleDutch meant for this work. It is not given to any personal account of a DoubleDutch employee. Access is shared by the team that is responsible for app publishing and management: App Operations.
For more information about Google Play Developer roles, click here.
The common actions that are carried out within a Google Play Developer account by a DoubleDutch App Operations Engineer are the following:
Create and update app listings (descriptions, images, name, etc)
Upload APK’s
Editing distribution details
Edit (if required by client) app availability
Edit app age rating
Unpublish/republish apps
All other aspects of the account are irrelevant to our work.
The reason why we advise clients to grant us Release Manager access is because it is the profile that encompasses all the activities we need to guarantee speedy publishing and troubleshooting if need be.
Inviting DoubleDutch as a Release Manager
To add DoubleDutch as a Release Manager:
Navigate to the Settings section from your Developer Console. You need to be logged in as the Account Owner (the email used to register for the account). Click 'Users & permissions'.
Click 'Users & permissions'. Then click 'Invite New User'.
Note: if you don't choose an access expiration date, DoubleDutch will have ongoing access to your Google Play Console account. This is the setting we recommend.
A pop-up will open that will prompt you to invite a new user via email address. Enter '[email protected]' as the email and choose 'Release manager' for Role. Then click 'Send Invitation'.
You will receive a confirmation email when DoubleDutch has accepted your invitation. Once the invitation is accepted, DoubleDutch is ready to distribute Android apps on your behalf.
View ArticleGo to Google Play Console and follow the on-screen instructions. It’s important that you are logged into the Google account that you want to be associated with your Google Play Console.
For more information about creating a Google Play Developer account, click here.
Note: we recommend using a company email address when creating yourDeveloper Accountinstead of a personal email address (i.e. Gmail). Google will often reject accounts registered with personal emails because of copyright infringement. In the same regard, the Developer Name you choose in the fourth step is public and displayed to customers in the Play Store. We suggest using your organization name and strongly advise against using your personal name or “DoubleDutch".
How to Fill in a Google Play Store App Listing
If you would likeDoubleDutch to publish your Android app on your behalf, continue to: Granting Google Play Developer Account Access to DoubleDutch
Or, if you're publishing your Android app on your own, continue to:
View ArticleIf there has been an upgrade or change made to your app, and you have elected to publish your Android app on your own, DoubleDutch will supply you with a new build of your app. It will have a higher version number, bug fixes, and/or possibly some feature enhancements. What you will want to do is upload it to the Google Play Developer Console and have it approved by Google as soon as possible so that your users can benefit from the upgrade.
First, log in to the Google Play Developer Console.
Next, locate your app in the app choices listed for your developer account. Click on the appropriate app.
Next, click on 'Release Management', then 'App Releases'.
"Set up your store listing"
To upload a new .APK file, click on 'Manage Production', then 'Create Release'.
Drag and drop the new .APK file into the 'APKs to add' section. You'll notice that the previous APK version will become deactivated. This is normal.
The release name will automatically update to the next appropriate version. For "What's new in the release?" you can put "Bug Fixes and Feature Enhancements".
Click 'Save', then 'Review' to proceed.
Finally, review the release information on the next screen. Then scroll down to the bottom and click 'Start Rollout to Production'.
You have finished your app update! This means that your app submission has been put into the review queue in Google’s review department. Typically, reviews of app updates take less time than new apps. However, it all depends on Google and their review queue. App update approval can take several days. It is advisable to take this into account when planning your app launch.
Note: during the app update process, you also have the opportunity to update things like your app name, icon, etc. To do this, you can follow the instructions on the Google Play developer site.
View ArticleWith Client Distribution for Android, your app will be distributed in the public Google Play Store. This is the most common way to distribute your app.
To get started, first, complete the app creation process in the CMS. DoubleDutch will build the app for you with a key and package name. Your DoubleDutch representative will send you an .apk file.
Then follow the steps below.
Note: click on the name of each step to view the process.
Step 1: Creating a Google Play Developer Account
Go to Google Play Console and follow the on-screen instructions. It’s important that you are logged into the Google account that you want to be associated with your Google Play Console.
For more information about creating a Google Play Developer account, click here.
Note: we recommend using a company email address when creating yourDeveloper Accountinstead of a personal email address (i.e. Gmail). Google will often reject accounts registered with personal emails because of copyright infringement. In the same regard, the Developer Name you choose in the fourth step is public and displayed to customers in the Play Store. We suggest using your organization name and strongly advise against using your personal name or “DoubleDutch".
Privacy Policy
Next, if you would like to have DoubleDutch publish your app, you cangrant DoubleDutch Release Manager access to your Google Play Developer Account. Follow the process in step 2a and we will publish the app on your behalf. Otherwise, skip to step 2b.
Step 2a: Granting Google Play Developer Account Access to DoubleDutch
Google Play Developer Access Overview
Per Google’s Terms and Conditions, DoubleDutch is not permitted to host customers’ apps in its own Google Play Developer account. Instead, using the Release Manager role, DoubleDutch can gain access to your Google Play Developer account. It allows us to work autonomously and get Android apps published, updated, or fixed as fast as possible.
Note: this role does not allow for changing any fundamental account information. That permission is restricted to the Google account that was registered with the creation of the Google Play Developer account. If necessary, it is possible to grant Release Manager access to only the app or apps created and managed by DoubleDutch. Also, this permission level is given to one functional account within DoubleDutch meant for this work. It is not given to any personal account of a DoubleDutch employee. Access is shared by the team that is responsible for app publishing and management: App Operations.
For more information about Google Play Developer roles, click here.
The common actions that are carried out within a Google Play Developer account by a DoubleDutch App Operations Engineer are the following:
Create and update app listings (descriptions, images, name, etc)
Upload APK’s
Editing distribution details
Edit (if required by client) app availability
Edit app age rating
Unpublish/republish apps
All other aspects of the account are irrelevant to our work.
The reason why we advise clients to grant us Release Manager access is because it is the profile that encompasses all the activities we need to guarantee speedy publishing and troubleshooting if need be.
Inviting DoubleDutch as a Release Manager
To add DoubleDutch as a Release Manager:
Navigate to the Settings section from your Developer Console. You need to be logged in as the Account Owner (the email used to register for the account). Click 'Users & permissions'.
Click 'Users & permissions'. Then click 'Invite New User'.
A pop-up will open that will prompt you to invite a new user via email address. Enter '[email protected]' as the email and choose 'Release manager' for Role. Then click 'Send Invitation'.
You will receive a confirmation email when DoubleDutch has accepted your invitation. Once the invitation is accepted, DoubleDutch is ready to distribute Android apps on your behalf.
If you are publishing the app on your own,you will create the app listing, upload all images and screenshots, upload the .apk file to Google Developer, and submit it for review. Follow the process in step 2b.
Step 2b: How to Fill in a Google Play Store App Listing
To publish an app in the Google Play Store you will need to create an app listing. The steps below will show you how to successfully fill in the app listing and submit your app for the first time.
Log into your Google Developer account.
Click on the button 'Create Application' in the top right.
Start by selecting the default language and filling in the app name in the popup window. Then click 'Create'.
Fill in the title (this is the app name that will be visible to users browsing the Play Store), short description, and the full description in the relevant fields.
Then upload the image assets to the relevant slots.
Scroll down and fill in the Categorization section. For Application Type, select 'Applications'. For Category, select 'Productivity'. We'll come back to the Content Rating after we upload the APK file.
Continue to scroll down and fill out the Contact Details and Privacy Policy. For the Privacy Policy, it's best to use theDoubleDutch.
Click 'Save Draft' to save your work.
Next, click on 'App Releases' in the left menu. Then click on 'Manage Production'.
Then click on 'Create Release'.
You will then be taken to a form to upload your APK file. Under the Google Play App Signing section, select 'Opt Out'. A pop-up will appear; click 'Confirm'.
Next, drag and drop the APK file you received from DoubleDutch into the "APKs to add" section. You'll notice that the release name will auto-populate.
Under "What's in this release?" it's recommended that you put "Bug Fixes and Feature Enhancements". Then, click 'Save'.
Next, click on 'Content Rating' in the left menu. There you will need to start a new questionnaire and fill in questions to determine the age rating of the app. Click 'Continue' to start the questionnaire. Then, input the email address you'd like to use for ratings related communications and select the App Category: Social Networking, Forums, and UGC Sharing.
Answers the questions on the next page by clicking the radio buttons, then click on 'Save Questionnaire', then 'Calculate Rating'.
Then the rating is shown on a new page. Scroll down and click on 'Apply Rating'.
Next, click on Pricing & Distribution in the left menu. The app’s price should be set as “Free”.
Also, make sure to have the app available in all countries. If you cannot, then make it available in the countries you wish and the Netherlands, USA, and Philippines these countries have our support teams who can help with issues when you report them. If you do not, our team will not be able to download the app and troubleshoot.
Then make click 'No' on the Primarily Child-Directed question and sure to click 'Yes' on the radio button to confirm that the app contains ads. The app offers the feature of Promoted Posts, which counts as in-app ads in Google’s criteria.
Scroll down in the Consent section, and check all the boxes.
Once all these fields are filled in, click 'Save Draft'.
After this, you should see four green check marks next to the following section names in the left menu: App Releases, Store Listing, Content Rating, and Pricing & Distribution. This means your app is ready to be published.
Click on 'App Releases' in the left menu. Then click 'Edit Release'. Then 'Review'. Review the release information on the next screen and then click on 'Start Rollout to Production' to submit your app for review.
You’re finished!
Note: it can take about several days for your app to be reviewed, please plan accordingly with your DoubleDutch representative.
View ArticleYou can hide sections of the app from view via the "Layout" tab of the CMS. This is helpful for sections that are "under construction" and are not quite ready for your attendees to see.
Hide an App Section
To hide an app section, uncheck the box next to an app section name to hide it. You'll note that this moves the app section to the "Disabled" of Alternatively, dragging the App Section into the "Hidden App Sections" area also does the trick.
Unhiding an App Section
To activate a section, simply check the box for that section, or drag the section back into the desired position in the visible part of the menu (e.g. Tab Navigation or Features).
When finished hiding/unhiding app sections make sure to click 'Save Changes'. You can preview what your app menu looks like to attendees via the phone to the right of the menu.
View ArticleClick one of the Guide Me buttons below for a guided walkthru of organizing app sections!
US
EU
Changing App Section Order
To change the order in which app sections appear in the app menu, first, go to the "Layout" tab of the CMS. Then, follow the instructions below:
Hover over an app section to activate the three-bar (a.k.a hamburger) icon. It will appear to the right of the text.
Click and drag the app section to the desired location in the menu.
You will see the change reflected in the phone preview to the right.
When finished, click ‘Save Changes’.
View ArticleTo configure settings specific to an app section (as opposed to general app settings which can be adjusted on via the "Basics" section of the "Setup" tab in the CMS), click on the app section in the "Layout" tab.
Leaderboard
From here you can:
Edit the section name:this must be a unique section name within the app menu (e.g. you can't have two sections both named "Agenda").
Change the icon:pick from the list or upload a custom icon by clicking ‘Upload Icon’. Artwork should be a 320x320 PNG file.
Allow check-ins from a status update: toggling this to "Yes" meanstheapp section will be listed as an option on the Status Update screen (e.g. attendees can easily associate an exhibitor or agenda session to their post). Enabling this feature encourages social sharing amongst the attendees in a structured way and provides you with insightful data since you can easily identify what attendees are talking about. Alternatively, attendees can check-in to individual items from this app section by navigating directly to each item.
Update screen prompt: customize the message that appears on attendees’ screens when theypost a status update.
Assign check-in points:set the number of points attendees will receive for interacting with this item by clicking on the points and adjusting the value. Points are tracked in the app section.
View ArticleWeb Views can be used tolink to a website or web-hosted document. Examples of Web View sections include linksto your company's Facebook page or Twitter feed.
Note:web addresses must be secured (https:// NOT http://)
As of July 2018, Web Views can be configured to open in different ways. Previously, the only option for creating these sections was to have the link open directly within the app.
Creating a Web View Section
To create a Web View section in the CMS, you first must add a section :
Go to the "Layout" tab and click 'Add a new section'.
Select the 'Web View' option.
Give the section a name.
Then click 'Save new section'.
Continuing from the "Layout" tab, click on the name of your new Web View section to configure it.
Web View Section Configuration Options
First, under the Page URL section, fill out the Web View URL you would like to link the section to in the app.
Note:web addresses must be secured (https:// NOT http://)
Next, choose the method for opening the Web View:
Default Web View: opens the web page within the event app.
External Browser: opens the web page with the phone's default browser app (e.g. Safari, Chrome).
Native App: attempts to open the web page in a native application (e.g. Instagram, Twitter). If the native app is not supported, a default Web View will be used.
Javascript SDK: opens a web page specialized for developers to create custom content. Provides basic integration hooks for receiving event information and customizing some UI.
Finally, select an icon from the options shown, or upload your icon. Then click 'Save Changes'.
Note: the aforementioned web view options are available on app versions 7.18 and higher. With the update to this app version, customers will no longer be able to disable sharing in an external browser. Previously created Web Views will default to using Chrome or Safari within the app, and will have the option to open in an external browser.
If you would like to prevent attendees from opening Web Views in an external browser, create a Web View section using the Javascript option, or create a dd://web urlwith "jssdk=true".
View ArticleThe event app comes pre-loaded with a standard set of sections that are most utilized by our customers, but you have the ability to customize your app menu with additional sections.
Click one of the Guide Me buttons below for a guided walkthru of adding an app section!
US
EU
Adding a New App Section
To add a new app section to your event:
Go to the "Layout" tab of the CMS and click ‘Add a New Section’
Select the type of section you would like to add (e.g. Web View).
Enter the name as you would like it to appear in your app. Note that we recommend limiting the section name to 18 characters. Section titles that contain more than 18 characters have a section of the title cut off.
Click the 'Save new section' button or press 'Return' on your keyboard. The newly created app section will thenappearin your app menu.
attendee groups
Once you've added a section, it can be configured further immediately upon clicking 'Save new section', or by clicking on the section title from the "Layout" tab.
Section Descriptions
A quick overview of the available app sections that you can add to your app:
Custom List:create an interactive list of item names and descriptions (e.g. create a "Local Attractions" list of nearby places of interest).
Web View:link to a website or web-hosted document. Attendees can access these sites right from the app (e.g. link to your Facebook page or Twitter feed). Note: web addresses must be secured (https:// NOT http://). For more details on using this section, please click here.
Info View:a single item showing basic information (editable HTML field) (e.g. create a "Conference Tips" section with wifi information, transportation details, etc.)
Folders:organize multiple lists by nesting them in folders. After creating a Folder, you are able to select and drag lists into it (e.g. create a folder called "What's nearby?", and then add in a Custom List called "Restaurants", a Custom List called"Golf Courses", and a Custom List called "Coffee Shops").
Files & External Links:upload one or more PDFs directly for attendees to access and download in the app, and/or link to one or more files hosted on the web. Make sure you use the full web address (https://). Note: files must be less than 30MB and web addresses must be secured (https:// NOT http://).
Exhibitors:this works the same as the exhibitor list that is already preloaded in the app menu. You can add additional ones if you want to separate out different kinds of exhibitors or sponsors.
Speakers:this works the same as the speaker list that is already preloaded in the app menu. You can add additional ones if you want to separate out different kinds of speakers.
Please note that while you have lots of options for customizing the look and functionality of your app menu, you cannot add any duplicatenative app sections such as attendee lists, activity feed, photo feed, interactive maps, surveys, or polls.
If you'd like the ability to differentiate among your attendee list, we recommend a few different options:
using the "" feature
hosting a PDF in the app with your groups listed that attendees can reference
View ArticleIntroducing Tab Bar Navigation
DoubleDutch uses Tab Bar Navigation forour in-app user interface.Tab Bar is a standard in the industry, adopted by popular apps such as Facebook, Twitter, LinkedIn, and Yelp. It offers improved in-app navigation, user engagement, and discoverability of key features without changing any functionality to the app.
There are five menu options persistent on the bottom of each screen:
The first two items, Activity Feed and Notifications, are permanent.
The third and fourth items can be customized with any item, such as Attendees, Agenda, etc.
The fifth item, the “More” button, leads to the additional menu items. Tapping on this button opens up a new page containing additional sections and settings.
Layout
Benefits of Tab Bar Navigation
The following are some of the benefits of an app that utilizes Tab Bar Navigation:
Optimizes Feature Discoverability
The most important features (such as the Activity Feed, Notifications, and more) are now visible right from any screen.
Improves App Navigation
Provides instant, one-tap access to the key menu items, which are visible on every screen.
Easily switch to view additional app sections and profile settings.
Increases User Engagement
Increased visibility to key functionality results in more user engagement.
Direct attention tounread notifications, so attendees don't miss a thing.
Tab Bar Navigation Configuration in the CMS
There are several options and things to keep in mind when configuring your tab bar navigation menu for your app in the CMS, via the tab:
Tab Bar Navigation Section
This section controls what appears in the navigation tab bar in the app.The first two sections, Activity and Notifications, cannot be changed or moved. Both Activity Feed and Notifications are crucial aspects of user engagement in the event app.The last two menu sectionscan be customized with any section such as Attendees, Agenda, Channels, Direct Messages, Custom Sections, and more.
View ArticleQR Code Hunt is a fun way to use gamification to drive engagement throughout your event. Attendees can scan QR codes and attempt to complete the scavenger hunt. Make the game even more competitive by awarding prizes for those that complete the hunt!
To enable QR Code Hunt for your event, go to the Discover More tab in the CMS and click 'Install Now'.
QR Code Hunt in the CMS
Once you have the feature enabled, you can go to the corresponding section in the CMS, under Content, to set up and configure QR Code Hunt.
Game Details
To set up the main details of your game, there are three text fields you will want to fill out:
Title: the name of the QR Code Hunt game
Game Instructions for Attendees: this will let attendees know what they need to do
Message to Attendee When Complete: the message attendees will receive when they complete the game
http://qrcode.kaywa.com/
Categories
Categories include a collection of codes that can be scanned. Maybe you want attendees to scan codes at exhibitor booths? Create an Exhibitor Booth category. Maybe you want attendees to scan a collection of codes to earn prizes? Create a Prize Earned category.
Enter the name of the category, then choose the number of scans required to complete that category.
Admins
Next, add admins to your game. These individuals will be able to add QR codes to the game.
Note: admins must be a listed as attendees in the app.
Adding QR Codes
To add QR codes as part of the game, you will first need to list yourself as an admin. Next, you will open the QR Hunt section in the app, and use the "Add Code" button to scan a code and have it automatically added to the game.
Note: to build your QR codes, you will want to find aQR code generator. For example, we recommend Kaywa QR Code: . When building the QR code, you can simply enter the name of the code you're creating in the URL field.
Once the code has been added, you will see it listed under the QR Codes box in the CMS. Here you can name the code as well as assign it to a category.
Attendees
The Attendees box shows the number of scans each attendee has completed. You can reset an attendee's scans back to zero by clicking on the 'Delete Scans' button to the right of an attendee's name.
You can also export the scan results by clicking on one of the export options: by category or by code.
QR Code Hunt in the App
To use QR Code Hunt in the app, attendees will go to the section in the app and tap 'Let's Play'.
On the next screen, they will see all the categories and number of scans required to complete the challenge.
Scanning a Code
To scana code, attendees will tap 'Scan Code' to open up the device's viewfinder. They'll then hover the viewfinder over the QR code to scan it.
Upon scanning the code, the attendee will receive a confirmation message that the code has been successfully scanned.
If the scan is the final one required to complete the challenge, the attendee will receive the congratulatory message. This is the same message that is created by the event organizer in the CMS.
Attendees can also view their game status by visiting the QR Hunt section at any time.
View ArticleThis section of the "Setup" tab allows you toset up and/or configure the emails that app users will receive regarding your event app. You can view samples of all these emails by clicking on the 'View Sample' link in the CMS.
Click one of the Guide Me buttons below for a guided walkthru of the Emails Section!
US
EU
Email Types
Welcome Email: sent to attendees in the CMS to inform them that your app is available to be downloaded and provides instructions on how to access it. You can send this to attendees by going to the "Content" tab in the CMS, clicking on the "Attendees" section, and then choosing 'Send Welcome' from the "Actions" menu. Please see this article for additional information on the Welcome Email.
After you make any changes to the settings of your emails, don't forget to click 'Save Changes'at the top.
Example Welcome Email
open registration
Note: there is no character limit when customizing the Welcome Email.
Signup Email: if your event is set to, users will receive this after signing into the app for the first time.
Example Signup Email
Note: there is no character limit when customizing the Signup Email.
Mid-Day Digest Email: this email sends a summary of your app's activity each day of your event around 1 p.m. local time of the event.
Day-End Digest Email: this email sends a summary of your app's activity each day of your event around 6 p.m. local time of the event.
Example Digest Email
Profile Views Email: when an attendee's profile is viewed in the app three or more times, they will receive this email notification informing them that other attendees are interested in their profile.
Example Profile Views Email
Reset Password Email: sent to a user when he/she resets the password used to access the app.
Example Reset Password Email
Exhibitor Dashboard Invite: sent to the exhibitor administrator to invite them to the exhibitor dashboard.
Example Exhibitor Dashboard Invite Email
View ArticleOpen or Closed Registration can be configured from the "Basics" section of the "Setup" tab in the CMS. The information below will help you decide which login option is best for your event(s).
Open Registration
If Open Registration is set to yes, anyone can self-register for the app simply by entering their email address to access the content, without any password initially required. The attendee will appear in your CMS as an attendee once they've logged in.
Login Flow
After entering their email, the attendee is sent a Sign-Up email (if enabled from the Emails section) with a few app tips and instructions on how to create their password. Note that they'll only need the password if they log out of the app on their device, or want to access the app from another device. Here is an example of the Sign Up email:
here
Note: Open Registration is not advisable for events using Lead Retrieval.
Closed Registration
If Open Registration is set to no, attendeesmust be preloaded in the CMS and pre-assigned a password. Please note that unless you are added to the CMS as an attendee, you will not be able to see the event in the app.
Login Flow
In order for the attendee to initially log in, they will need to receive their password. We provide a Welcome Email in our CMS that can be sent to all attendees toprovide them with their password and a link to download the mobile app. Here is an example of the Welcome Email :
More information on customizing and sending the Welcome Email can be found .
After downloading the app, users will enter their email and then be prompted for the password that was assigned to them upon account creation.
If the user has customized their password in a previous event in your app, their password will remain the customized password and will not be overwritten by the new event's password unless you use the "Set all attendees passwords" option in the 'Actions' drop-down menu on the attendee section of the CMS.
Note: Closed Registration is not advisable for events with a lot of attendeesregistering for the eventon-site.
Switching fromClosed to Open Registration
Login Flow
If the registration type is changed from Closed to Open Registration and your attendee list is already uploaded to the CMS, these attendees will still be required to input the password you've provided for them. To allow theseattendees to initially log in without a password, you will need to delete the attendee list inthe CMS.
Note: deleting attendees will erase any data related to the attendee including status updates, survey responses, points, achievements,and any other content or action.
View ArticleIn the first section of the "Setup" tab you'll be able to see and adjustthe details related to your event app.
Click one of the Guide Me button below for a guided walkthru of the Basics section!
US
EU
BasicDetails
here
Download App:the unique download page where you can access the iOS, Android, and HTML5 versions of your app.
Event Description: the short description that will display under the name of your event when users log in to the app.
Start and End Date:the start and end date of your event.
Time Zone: the time zone that your event will be taking place. Please read this article for more about the importance of the time zone settings.
Unique Identifier:entering an ID of your choosing will generate the ID on exportable reports for easier report tracking.
Event Type:the type of event you're having (e.g. Conference).
Icons & Colors
Primary Color:the main color that is displayed throughout the app in the header, linked text, and buttons. A darker color works best to contrast against the white areas of the app.
Icon Color: The color of theiconsin the app's navigation menu. A darker color works best to contrast against the white background of the menu.
Note: uploaded icons (via the "Layout" tab of the CMS) will appear in the color they were uploaded, NOT the icon color you've chosen in the CMS.
Event Icon:appears on the event selection screen. The image must be a 512x512 .png file. Simple images with no text work best.
Header Image:appears at the top of the Activity Feed on iOS devices. The image must be a 300x60 .png file with a transparent background.
Configuration
Open Registration: if set to yes, anyone is able to download the app and create a login to access the content. They will appear in your CMS as an attendee once they've logged in. If set to no, a user must be included on your attendee listin the CMS in order to access the app. Click here to read more about choosing between open and closed registration.
Enable Ratings: if set to yes, all agenda items will have a "Rate & Review" button for users to provide a 1-5 star rating with comments. If set to no, this button will not appear.
Enable My Agenda: if set to yes, users will be able to create a personalized agenda by selecting items from the main agenda to add to the "My Agenda" view. If set to no, users will only be able to see the agenda you upload.
Hide attendee list:if set to yes, the full attendee list will not be available for users to view, however, they will be able to search for a specific user profile. If set to no, the full attendee list will be visible to users in the app.
Enable Session Notes:if set to yes, all agenda sessions will include the ability for attendees to take notes in the app and email the notes to themselves.
Hide Default Achievements:if set to yes, the default achievements will be disabled and only any custom achievements which you've created in the CMS will be available to be earned.
Show User Achievements:if set to yes, earned achievements will display on the attendee profile.
Enable Session Notifications:if set to yes, attendees will receive a notification on their device reminding them of the upcoming start time for each session they have bookmarked.
Session Recommendations:if set to yes, recommendations will appear in the app for upcoming sessions to attend. Learn more here.
Attendee Recommendations:if set to yes, recommendations will appear in the app for other attendees to follow. Learn more .
Exhibitor Request Information Enabled:if set to yes,attendees will be able to requestinformation from exhibitors via a button on the exhibitor profile. Attendees who tap the button will appear on the exhibitor's lead report.
Exhibitor Messaging Enabled:if set to yes, attendees will be able to send an email message via a button on the exhibitor profile. An email will be sent to all booth staff associated with the exhibitor.
Enable Bookmarking:if set to yes, attendees will be able to bookmark any list items including exhibitors and speakers. Bookmarks can be found in the Bookmarks section of the app menu. (Note that bookmarked sessions will appear in the "My Agenda" section of the app.)
Now Button Enabled: no longer functional. Do not use.
Download all files:if you have a lot of files (or large files) loaded into your app that you want to ensure attendees will be able to access them without issue, you can set this to yes. Attendees will be prompted to download files from agenda sessions and file sectionsat their first login, so they can access them offline later.
View ArticleThe Content Management System, or CMS, is the web-based system you will be using to load all the content into your app, configure different settings, and view performance data from your event. Below is a brief overview of the tabs you'll navigate between.
Note: please be aware that the DoubleDutch CMS is optimized for performance using the Google Chrome browser. You can download Google Chrome for free here.
Layout:the "Layout" tab allows you toadd or remove sections in the app menu, choose their arrangement, and edit icons and the color scheme. You can also choose which sections are live for attendees to see and which are hidden from view.
Content:add and edit content that goes in each app section such as your agenda and attendee lists.
Setup:configure basic and advanced settings such as your color scheme, email communication to attendees, and gamification options.
Event Day:the "Event Day" tab gives you quick access to tools you need most while at your event such as Gameday, attendee search, push notification and promoted post message creation, and the activity feed.
Event Performance:the "Event Performance" tab allows you to track usage of your app in real-time and run detailed reports about your event.
Discover More:discover new features by installing extensions directly into your event. Some of these features include Live Q&A, Digital Business Cards, and Trivia Challenge.
Support:links directly to the Customer Support Center.
View ArticleThe Customer Advisory Board template is designed to provide your attendees with all the information they need to have a seamless experience. In addition to our most popular app sections (e.g. activity feed, agenda, speakers, and maps), we’ve added a few informational sections that commonly apply to internal meetings and seminars:
A Message from the CEO*
Event Details*
Surveys*
Polls*
Files & Documents*
*Denotes sections that need your review. We’ve created some content for you, but don’t forget to add content as it applies to your event!
Content to Note
The Customer Advisory Board template also includes pre-created push notifications and promoted posts as well as engaging polls and generic feedback surveys. Update the dates and times of the messages, surveys, and polls to be live during your event. Add your own messages to build out and customize the communication plan within the app!
Additional Recommendations
Customer Advisory Boards are all about connecting with your key clients and prospects, letting them know what's going on in your company and creating strong brand advocacy and customer retention. As an event organizer, you have the power to inform and reinforce this by creating promoted posts and push notifications directing your attendees to key sections within the app throughout the event.
You can also choose to enable the most effective tools for networking, the Direct Messaging and Topic Channels sections. Ideas for Topic Channels include Meet our Team, Product Enhancements, and Best Product Experiences.
View ArticleThe Executive Summit template is designed to provide your attendees with all the information they need to have a seamless experience. In addition to our most popular app sections (e.g. activity feed, agenda, speakers, and maps), we’ve added a few informational sections that commonly apply to executive summits:
Event Details*
Surveys*
Polls*
Files & Documents*
*Denotes sections that need your review. We’ve created some content for you, but don’t forget to add content as it applies to your event!
Content to Note
The Executive Summit template also includes pre-created push notifications and promoted posts as well as engaging polls and generic feedback surveys. Update the dates and times of the messages, surveys, and polls to be live during your event. Add your own messages to build out and customize the communication plan within the app!
Additional Recommendations
Executive Summits are all about having information distribution and retention. As an event organizer, you have the power to inform and reinforce this by creating promoted posts and push notifications directing your attendees to where resources and information can be found both within the app and outside. Don’t forget to take advantage of the Files & Documents section to upload supplemental materials.
You can also choose to enable the most effective tools for networking, the Direct Messaging and Topic Channels sections. Ideas for Topic Channels includeIndustry Trends, Economic Resources, and Challenges.
View Article
