Blazheiev Vitalii. - iOS Venture Apps

Table of content:

I. Creating IOS application

1. Ideas
2. Design Programming: Mockups
3. Client Server in iOS
4. Essence Scrum Process
5. Prototyping
6. Feature: Alpha, Beta, Final
7. Revenue and monetization
8. Submit to AppleStore
9. Internet Marketing

II. Venture

What is venture?

Funding stages

Finding investor

Author : Vitalii Blazheiev

ISBN #: 978-1-329-90114-8

Book Title: iOS Venture Apps

Toronto, Canada, 2016

It s not a secret that any idea , which came to your mind , comes to the mind of somebody else at the same time. If you will not implement it, somebody else will do it. I had this on my own experience dozens of times and I found solution. I decided to save my ideas at idea stage and come back anytime I have time for it. Additionally I am visual and my mind reinterprets every eureka! in picture - pictures have to do with how we think :) It was like this until I came to the point where I sat down and painted my first sketch, to be more precisely first skeleton of sketch Then added more details, once again, added content and voila . Idea was painted with simple grey pencil and ready to be stored for my whole life at authentic A4 paper. It was beautiful for me because it was done by me, and I knew every peace of it, since I did it by myself. Now I could have come back to sketch any time I wanted. Its later, when sketch will become my project, I will choose main components which forms the s ystem, analyze features, add tasks, will drop some priorities and start working on it every day!

Ideas come to our heads and go out all the time - during we think, read, talk or doing something completely opposite from sitting down and sketching on the paper. That is why tools like iPhone or iPad are invaluable for this, since they are always with us, especially with Internet connection to sync sketched ideas with cloud service and possible version control. As for me the best beginning starts with mandate, ideas as well. We formulate short sentence, which emphasize the whole breakthrough and start performing business analysis on the subject domain. Be that verb analysis or classic analysis but we must to have main abstractions together and composition between classes done to have crystal clear systematic vision. Another thing its when we paint - everything happens totally natural, using smooth lines between one logical point to another.

At the time when I was painting my first sketch, I was totally involved and inspired by process. I was looking for the technology to keep me focused on one concrete goal, combining discovery with synthesizing skills. The tool, which let me express my breakthrough and leave it done, totally finished. Just paint it, add music and become total owner of new brilliant idea And I have created Essence Sketch: to have ideas saved and materialized.

Short notes and words were not enough and I decided to paint my vision, wrap phrases in my emotions and deliver packaged as trans media presentation. Once its done - its done! Idea always available online and licensed. Share it with friends to get feedbacks and improve your concepts. Sell it all together for million $ , or get payed for use as part of others project, using your license via Es sence Service: create, publish and own ideas. Now, lets talk about how do we actually do #1 apps and software products.

Main idea in design programming is to separate design from coding phases since coding itself, thats what called programming becomes very simple task when design is final and there is technical design with class names and relationship . We can think this way to deliver feature we need to have design with requirements, technical design with solution and code, which reinterprets technical design to the computer.

Design of requirements is a goal driven process, which precisely describes what do we want to have done and this is the best when designers are trying not to be programmers or to think like programmers, but let it flow. Perfect example is game industry people are working in the huge teams, sometime up to 400 people, and need to deliver fun. You know that its complicated to measure fun for all of us, but they do, they deliver and this approach is called design driven process . In design driven projects, person in charge of feature sometime doesnt know anything about existing of programming language, but knows what exactly feature should do and how its components works together.

If technical design is the bridge between creative design and coding itself, I would use the same programming method for design and implementation: prototype, alfa, beta and final product. This is more comes from scrum, which keeps integrity of the project and parts which are being developed are constantly integrated into the final project at least at the end of the scrum and iteration over iteration incrementally improves prototype.

Speaking about Blue Prints this is the highest version of design, which is final, the most precise and looks like HD photo of what should be done. This is my favorite method to have such a nice visualization. We used Blue Prints wor king with Bombardier and SAP .

Results of the projects are speaking for themselves. Additionally, if Blue Print is the result of many design iterations, what were those iterations? Find please design step-by-step below:

1. Outline defines boundaries of the software and indicate main plan
2. Sketch shows main components of the system and has painted vision
3. WireFrame contains geography of the system and gives clear understanding
4. Mockup pixel perfect output of design

After design stage , any developer is dreaming to have functioning prototype with required behavior of the system. Exactly, the only difference what makes prototype different from design outputs is behavior and to develo p it we need to do some coding to put things together.

In programming world there are two types of system composition: composition classes and decomposition of objects and to describe them in objective-c or c++ we need to grasp them from the task domain created by designers. Indeed we just need to look at our mockups and technical description from analysis point of view.

Btw, I always print mockups and write with my pen on top of it, put notes, names of the classes, dependencies and so on. This writing I call iteration of technical design and I perform it with ritual :

1. Make every noun from the text or name and make class name
2. Make every verb a function and put it to the appropriate class
3. Pain t decomposition from left to right which class owns whom

Make marks on the mockup , correct names and print mockup again.

I think almost all iOS apps should have online component these days: to share content or to execute complicated logic at the server That is why client server paradigm is mandatory to know. Online and internet brings totally new marketing and every product tends towards service oriented solution used by customer. Its totally centralized and if application designed properly makes everything so much easier up to anti-cheat protection, putting all business logic to the servers, like games already do.

All those fancy wor ds: marketing, service, account, online community prove s that client server applications are software of 21 century and comparing to desktop software always require internet connection to be on top.