Smartphone Proposal (2011)
From UG
m (moved Smartphone Proposal to Smartphone Proposal (2011)) |
|||
| (4 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Smartphone App]] | [[Category:Smartphone App]] | ||
| - | <center>Proposal for Implementation</center> | + | <center><big><b>Proposal for Implementation</b></big></center> |
== Assumptions == | == Assumptions == | ||
| Line 43: | Line 43: | ||
== Project Plan == | == Project Plan == | ||
| + | {| {{table}} border="1" | ||
| + | | align="center" style="background:#f0f0f0;"|'''id''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''Summary''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''N''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''Sprint''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''Sprint''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''Sprint''' | ||
| + | |- | ||
| + | | ||||||June-July||July-Aug||Aug-Sep | ||
| + | |- | ||
| + | | 0.||''Phase 0:'' Research, Proposal||||<center>'''x'''</center>|||| | ||
| + | |- | ||
| + | | 1.||''Phase 1:'' Preliminary development works||||||<center>'''x'''</center>|| | ||
| + | |- | ||
| + | | 2.||''Phase 2:'' Proof of Concept||||||||<center>'''x'''</center> | ||
| + | |- | ||
| + | | 3.||''Phase 3:'' [[TBD]]|||||||| | ||
| + | |- | ||
| + | |} | ||
== See also == | == See also == | ||
[[Smartphone_App|Requirements]]. | [[Smartphone_App|Requirements]]. | ||
Current revision as of 18:30, 25 April 2012
Contents |
[edit] Assumptions
We assume that support should be provided in the following order:
- iPhones (on iOS mobile operation system).
- Blackberry smartphones.
- devices on Coogle’s Android.
[edit] Summary
Support for each operation system (OS) requires developing separate application and also their own distribution to clients. Development of smartphone application requires special application programming interface (API). In some cases special hardware is needed.
There are two forms of smartphone application – native and web-based. Each of them has its own advantages:
- native application more fully uses all resources of device but requires obligatory updates to get new features and involves more costs and time for backward compatibility and bugfix process;
- web-based application is more flexible and doesn't depend on OS but has restrictions that are conditioned by browser capabilities.
Therefore it is suggested to implement core features in native part of SmartApp. Web-based part can provide additional capabilities.
[edit] Implementation Concept
- Divide development process into phases according to implemented features.
- Spread SmartApp features across native and web-based implementation:
- native part of Application – one for each OS.
- web-based part of Application – for all OS.
[edit] Phase 1 (Proof of Concept)
- Concentrate first on iPhone native application and web-based part of SmartApp that is common for all platforms.
- Native features for Phase 1:
- Login / Logoff.
- Top 5 from Watch list (like in Client App).
- Web-based features for Phase 1 – CT detailed view and other basic functionality TBD.
[edit] Associated Costs
In order to develop an application for iPhone need to use integrated development environment (IDE) that works only on Apple computer. Therefore, to provide full circle of developing and testing for CT2 Smartphone Application is proposed to purchase:
- Apple dev computer: 15-inch MacBookPro - $1978.
- Unlocked iPhone for testing - $649.
- iOS Developer Program (Company subscription) – $99/year.
Total: $2627 one time and $99 per year of development/support.
[edit] Additional Questions
- Define set of CT fields for viewing in SmartApp in Phase 1.
- Do we need support the devices on Nokia’s Symbian OS?
[edit] Project Plan
| id | Summary | N | Sprint | Sprint | Sprint |
| June-July | July-Aug | Aug-Sep | |||
| 0. | Phase 0: Research, Proposal | ||||
| 1. | Phase 1: Preliminary development works | ||||
| 2. | Phase 2: Proof of Concept | ||||
| 3. | Phase 3: TBD |
