Skip to content

iOS Application Publication Guide

Doug Salvati edited this page Jun 29, 2017 · 4 revisions

This guide is designed for those picking up iOS application publication to get started. Before publishing an iOS application, there are several guidelines you must follow. These are all listed below.

Access to an iOS Developer Account

In order to publish iOS applications, we need access to a paid iOS Developer account (currently stipulated at $99/yr). The account we use for development is an iOS University Developer account and does not have permission to publish applications to the Apple App Store. Therefore, the iSENSE team will be publishing all iOS applications through the University of Massachusetts Lowell's iOS Develop account.

Forms

The University first requires us to fill out a software disclosure form to get the apps in their system. A separate form must be filled out for every individual app.

The software disclosure form asks you to attach any third-party license to the form when submitting. We do use third party code, so do not forget this step. As of this writing, we use the DLAAlertView and Toast classes provided at the linked Github repositories. Each of these repositories linked will have a license file that you are to copy and attach to the CVIP disclosure form. Additionally, you should check through both your app and the iOS API to ensure no additional third-party code has been utilized. In the event that you find additional third-party code, edit this Wiki to include it above and attach the license(s) to the CVIP form as well.

Branding

Every iOS application must have a splash screen that matches the app's icon theme. Please follow the exact template as below:

Sample icon:

icon

Sample splash screen:

splash

Review

The University software team will not publish your application until you submit a Github repository link to them via email for personal review. Be prompt and fix everything they request to speed up the provisioning process. The email to submit to will be dependent on who currently works for that team (we submit to their personal emails, not a unified email), so you will have to figure this out on your own.

In addition to the link to our repository, be sure to also attach a few sample screenshots of the application running. It must be stressed that you ensure our application is not pushing to dev before submitting it to this team. The application in our repo should always be configured to push to live.

Open Source License

iSENSE is published under the BSD 3-clause license. Therefore, you should include the license exactly as follows at the top of every original source file in your iOS application:

/*
 * iSENSE Project - isenseproject.org
 * This file is part of the iSENSE iOS API and applications.
 *
 * Copyright (c) 2015, University of Massachusetts Lowell. All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions are met:
 *
 * Redistributions of source code must retain the above copyright notice, this
 * list of conditions and the following disclaimer. Redistributions in binary
 * form must reproduce the above copyright notice, this list of conditions and
 * the following disclaimer in the documentation and/or other materials
 * provided with the distribution. Neither the name of the University of
 * Massachusetts Lowell nor the names of its contributors may be used to
 * endorse or promote products derived from this software without specific
 * prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
 * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
 * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
 * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
 * DAMAGE.
 *
 * BSD 3-Clause License
 * http://opensource.org/licenses/BSD-3-Clause
 *
 * Our work is supported by grants DRL-0735597, DRL-0735592, DRL-0546513, IIS-1123998,
 * and IIS-1123972 from the National Science Foundation and a gift from Google Inc.
 *
 */

Make sure that items such as the copyright year and grants are always up to date before submitting the application for approval.

Do not put this license on top of any source file not originally by us.

When in Doubt...

Use iOS Motion or iOS Writer as a basis for your own app. Perform in-house testing before distributing it for review.

Clone this wiki locally