Mobile Application

Get Started. It's Free
or sign up with your email address
Mobile Application by Mind Map: Mobile Application

1. For whom

1.1. Mobile app users/end customers

2. stakeholders

2.1. VCs of the company

2.2. Shareholders of company

3. Who will do

3.1. People in the organisation

3.1.1. UI designers

3.1.2. Backend developers

3.1.3. Testers

3.1.4. Sales team

3.1.5. Marketing team

3.1.6. localization team

3.2. Project manager

3.2.1. Ankit

4. iPhone and iPad

5. Android

6. Budget

6.1. 50 Million JPY

7. Milestones

7.1. Project start - July 16

7.2. Project charter approved - Mid July 16

7.3. Approval of hiring new resources - Mid Aug

7.4. New hires on board - Oct 16

7.5. POC app - Oct 16

7.6. 80% app done (including testing) - May 17

7.7. Get Certification of app - Sep 17

7.8. Launch of app - Oct 17

7.9. Post release support - till Oct 18

8. Where

8.1. Japan, HQ of the company

8.2. Other markets

8.2.1. APAC

8.2.2. USA

8.2.3. India

8.2.4. Europe

9. Scope

9.1. Twonky application

9.1.1. Features

9.1.1.1. Premium features

9.1.1.1.1. Saving user's favorite, song , movie preferences for premium users

9.1.1.1.2. Option of uploading data to cloud

9.1.1.1.3. Ability to transfer/render/play content from app to any device

9.1.1.1.4. Customer support for issues encountered

9.1.1.1.5. Maintaining user history

9.1.1.1.6. Rendering/transferring multiple files to multiple devices

9.1.1.1.7. No speed limit while transfering

9.1.1.1.8. Color themes

9.1.1.2. Free features

9.1.1.2.1. Transfer/render content one file at a time to one device

9.1.2. Payment plan options

9.1.2.1. Weekly

9.1.2.1.1. 1000 JPY

9.1.2.2. Monthly

9.1.2.2.1. 4000 JPY

9.1.2.3. Yearly

9.1.2.3.1. 45,000 JPY

10. Why

10.1. The app aligns with company value of being leader in mobile app landscape for wireless transfer

10.2. There is no existing application like this in the market

11. Risks

11.1. First movers advantage

11.2. Cannot get certification

11.3. Users dont like the app

11.4. Another new mobile platform comes

11.5. Movement of resources

11.6. Stealing code by disgruntled employees

11.7. New protocol standard  comes

12. Success criteria

12.1. Number of downloads

12.1.1. Japan = 2 Million

12.1.2. India = 500K

12.1.3. US = 4 Million

12.1.4. Europe = 1 Million

12.1.5. APAC = 3 Million

12.2. Number of users opting for advanced features

12.2.1. Japan = 500K

12.2.2. India = 50K

12.2.3. US = 1 Million

12.2.4. Europe = 100K

12.2.5. APAC = 100K

12.3. Able to get certification from external agency that this app will work with digital devices

13. Change control authority

13.1. Rep. of VCs of company

13.2. Shareholders of company

13.3. Steering committee