---
title: 'Project documentation template'
disqus: hackmd
---
Your Developer Account
===



## Table of Contents
[TOC]
## Helpful Links
Keep these links handy!
1. Guide on getting your DUNS Number: https://m.wikihow.com/Acquire-a-DUNS-Number
2. Application Page: https://www.dnb.com/duns-number/get-a-duns.html
The Process
---
Hi SwingU Client,
We are glad to have you as a partner and as SwingU starts to develop your app there are certain materials the development team will need to have in order to keep the process on schedule. The following is a list of what is needed.
>CUSTOMER ACCOUNTS REQUIRED:
- DUNS Number: in order to establish an App Store account, you will need to apply for a DUNS number. Many established businesses already have one assigned so be sure to check before applying and waiting. It would be a 9-digit number. Here are some helpful links on the process and we are here to help. IT IS VERY IMPORTANT THAT THIS REQUIREMENT IS MET AT THE BEGINNING OF THE APP BUILD PROCESS, ALL OTHER DEVELOPMENT CAN BE SLOWED OR HALTED AND LAUNCH DATES CAN BE COMPROMISED.
Guide on getting your DUNS Number: https://m.wikihow.com/Acquire-a-DUNS-Number
Application Page: https://www.dnb.com/duns-number/get-a-duns.html
- App Store Account: You and your business will always be in control of the accounts and intellectual property. What we need is to have an App Store Developer Account created and then the SwingU development team assigned within the account. Here are some helpful links and this process will be done in conjunction with the SwingU Development, led by Adam West. For this, we will need your Apple ID and will walk through it via screen share.
Guide for creating the account: https://developer.apple.com/programs/enroll/
- Google Play Store Account:This process will be less intense than establishing an account in the App Store.
Steps for creating account: https://support.google.com/googleplay/android-developer/answer/6112435?hl=en
CUSTOMER MATERIALS REQUIRED:
- Branding: provide current logo art along with specific brand color details. This allows the design team to implement the correct icon, splash screen, and headers for the app. We would also need the specific name or title of the app since this sometimes differs from the instructor’s name or facility.
- General Instructor Info: provide all general instructor information that the application will be required to host so that it may be pre-populated into the app
- Modules & Features: have all features and modules that are desired listed, along with placement in the app
- Lesson Booking: provide access to documents displaying how the current lesson booking system is documented and functioning
- Email & Contact Info for Customer: provide email and DUNS Number from which to establish Apple and Google Play SwingU Accounts for Customer; also provide SMTP information for sending Customer emails via Customer’s domain
- Privacy Policy and Terms of Use: provide privacy policy and terms of use to be displayed to users of the App
- Content Library: provide access to video- and media-storage system with video content, tagged for category, sub-category and access level (free users, paid subscribers)
All of this will be covered in our kick-off call and we can answer any questions, expand on any areas where you may have questions, along with talking features, strategy/launch date for your branded app.
Attached you will find a copy of the software license agreement for your review and I will send another copy for your e-signature; again there is no money due up front. Also, there is a PDF that covers the tools and features of the app.
Let’s Get This App Built!
> Read more about sequence-diagrams here: http://bramp.github.io/js-sequence-diagrams/
Project Timeline (Example)
---
```mermaid
gantt
title A Gantt Diagram
section Client Tasks
A task :a1, 2020-12-01, 30d
Another task :after a1 , 20d
section SwingU Tasks
Task in sec :2020-12-12 , 12d
anther task : 24d
```
> Read more about mermaid here: http://mermaid-js.github.io/mermaid/
## Appendix and FAQ
:::info
**Find this document incomplete?** Leave a comment!
:::
###### tags: `Templates` `Documentation`