자기 자신이 해낸 것을 즐기는, 그리고 자기 자신이 하고 있는 것을 즐기는 사람은 행복한 사람이다. - 괴테 -
자기 자신이 해낸 것을 즐기는, 그리고 자기 자신이 하고 있는 것을 즐기는 사람은 행복한 사람이다. - 괴테 -
날씨가 흐리다.
슈슈는 감기때문에 오늘도 결석.
5시 50분에 나와서 6시 5분 입수.
체조 잠깐 하고.
자유형 4
배영 킥 3
배영 4
배영 4
접영 4
접영 6
접영 4
한바퀴 걷고
스타트 자유형 10?
스타트 평영 6
출석률이 좋다.
2013.03.25 수영일지 (0) | 2013.03.25 |
---|---|
2013.03.23 수영일지 (0) | 2013.03.23 |
2013.03.21 수영일지 (0) | 2013.03.21 |
2013.03.20 (0) | 2013.03.20 |
2013.03.19 수영일지 (0) | 2013.03.19 |
[CSS] daum 사이트의 responsive (0) | 2013.04.08 |
---|---|
[Design] 40+ Seriously Creative 404 File Not Found Pages (0) | 2013.04.05 |
[HTML5] 더 나은 웹 사이트를 만드는 데 도움을 줄 수있는 25 웹 개발 자원 (0) | 2013.03.13 |
[iPad] Sencha animator 이용해서 iBooks Author 만들기 (0) | 2013.01.04 |
[Style] 유니코드심볼 - http://panmental.de/symbols/info.htm (0) | 2013.01.03 |
Mobile Programming Models
Web
Web applications on mobile devices developed using the web model are accessed using a mobile browser.
A primary advantage of the web model is its multiple platform support, allowing your app to reach the broadest audience of mobile users. The code written using standard web application development languages can deliver a similar end user experience across multiple devices and operating systems. The web model approach also permits your development team to be more agile in addressing and fixing problems. Updates to the mobile application can be made easily over the web as opposed to having to release an update through the App Store for iOS apps and Google’s Market Place for Android apps.
Despite the potential of web technology in the mobile arena, there are limitations. One challenge facing developers is emulating the user interface and experience of a native application within the browser and providing cross browser compatibility. It is worth noting, however, there is a growing ecosystem of third party tools and frameworks such as Dojo Mobile, jQuery Mobile, Zurb Foundation, Less Framework 4, and ResponsiveJS providing developers with solutions to common interface problems. Web apps cannot access all of the device’s hardware and software, such as the address book or the notifications in non-webkit supported browsers. Creating a hybrid application, discussed in the next section, can circumvent these disadvantages.
A web approach is ideal if you are trying to reach the largest audience and not isolate a subset of your user base. The web model is also optimal if development and maintenance costs are paramount. Web development skills are more common than native development skill sets. Many organizations already possess in-house developers with experience in web application development.
Hybrid
Hybrid applications are programmed using the same web technologies as the web model, but are packaged and distributed as native applications. A hybrid application is essentially a web application wrapped in a native shell. Hybrid applications can leverage a Web Developer’s existing skillset and tap into a limited subset of the device’s native hardware. Several popular mobile web application frameworks are PhoneGap, Sencha Touch, and Appcelerator Titanium.
There is a caveat, hybrid applications must still be compiled and deployed through the target platform’s method of distribution. For instance, to distribute your app through the Apple App Store, you would need to build and compile your application using XCode and adhere to Apple’s guidelines and clandestine approval process. To target Android devices, you would further need to compile and distribute your application using Eclipse and the Android SDK then distribute your application in Google’s Market Place. It is worth noting, Adobe’s PhoneGap Build system enables developers to upload their assets (HTML5, CSS, JavaScript) to Adobe’s Cloud service and have their apps compiled using the latest PhoneGap SDK.
A hybrid approach is recommended if your application requires access to native functionality such as the device’s address book, or file system and it is essential for your application to target multiple platforms in addition to long-term maintenance and feature enhancements.
Esri’s ArcGIS API for JavaScript can be used to build hybrid applications. The same workflow for building your application using the web model can be applied to the hybrid model. You would import the compact build of the Esri JS API and any additional libraries (Dojo, jQuery, etc). Cascading style sheets can still be used to apply styles to your application’s user interface. Testing your hybrid application would require running it in a simulator or a device.
Native
Native applications are binary executable programs installed on the device. There is a different SDK for each mobile operating system. Native application development must use a language specific to the platform in which the application is deployed.
Although the native model excels in performance and low-level device hardware access, a critical disadvantage of native development is portability. Code written for one mobile operating system cannot be reused for another mobile operating system. A team would need to learn multiple programming languages, software development kits (Esri offers the iOS, Android, and Windows SDK) and manage several codebases. This makes development and maintenance potentially costly and time consuming.
The native model may be the best approach for your organization if the user interface requirements are strict and the native functionality essential.
Another scenario would be a case where organizations intend to only release their app to a subset of the target audience, and therefore target only a single mobile OS. For example, consider a private internal application only available to employees issued a specific mobile device (i.e. iPhone). This would be an instance where it may not make sense to develop for multiple platforms.
The following table summarizes some of the benefits and limitations of each of the three models and also serves as a decision matrix in helping you chose the most appropriate model for you application.
[javascript] Knockout.js (0) | 2013.03.22 |
---|---|
[jQuery] jQuery UI - Slide Scroll (0) | 2013.03.22 |
[javascript] Meteor - nodejs . meteor (0) | 2013.03.20 |
[jQuery] Collection of jQuery Drag and Drop Plugins (0) | 2013.03.20 |
[javascript] Image Upload with Preview and Delete & mobile (0) | 2013.03.19 |
다이아몬드를 찾는 사람이 진흙과 수렁에서 분투해야하는 이유는 이미 다듬어진 돌 속에서는 찾을 수 없기 때문이다.
다이아몬드는 만들어지는 것이다.
- 헨리 B. 윌슨 -
최선을 다하고자 결심하는 순간, 신도 감동을 받는다.
결코 상상할 수 없는 여러 가지 일들이 나를 도와준다.
결정의 순간을 시작으로 수많은 사건들이 일어나며,
어떤 누구도 자신에게 이런 일이 일어날 거라고 생각하지 못했던
온갖 종류의 예기치 않던 사건들과 만남과 물질적 원조가
나의 힘이 되어준다.
-요한 볼프강 폰 괴테
‘재능 있는 사람이 가끔 무능하게 행동하는 것은,
그 성격이 우유부단한 데에 있다.
망설이는 것보다 실패가 낫다.’(버트란트 러셀)
고민이란 어떤 일을 시작했기 때문에 생기기보단
할까 말까 망설이는 데서 더 많이 생깁니다.
모든 일은 망설이는 것보다
불완전한 상태로 시작하는 것이 한 걸음 앞서는 것이 됩니다.
꾸준한 노력을 실력이라 부른다. (0) | 2013.03.25 |
---|---|
일이 즐거울 때 인생은 기쁨이다. (0) | 2013.03.22 |
견디기 힘든 것은 좋은 날씨의 연속이다. (0) | 2013.03.20 |
낙담하지 말라 (0) | 2013.03.19 |
많이 주는 자가 부자이다. (0) | 2013.03.18 |
내 마음의 꽃밭 (0) | 2013.03.23 |
---|---|
'선택의 여지가 없었어요' (0) | 2013.03.22 |
기꺼이 '깨지는 알' (0) | 2013.03.20 |
'꿈춤' (0) | 2013.03.19 |
고비마다 나를 살린 책 (0) | 2013.03.18 |
날씨가 영하 4도.
갑자기 추워졌다.
1번 레인에 아주머니부대는 거의 전멸.
6시 5분 입수.
자유형 4
오리발 착용.
자유형 8
자유형 1분 인터벌 5
배영킥 4
배영 4
배영 4
한바퀴 걷고
접영 4
접영 50m 3
쉽지 않은데~
2013.03.23 수영일지 (0) | 2013.03.23 |
---|---|
2013.03.22 수영일지 (0) | 2013.03.22 |
2013.03.20 (0) | 2013.03.20 |
2013.03.19 수영일지 (0) | 2013.03.19 |
2013.03.17 수영일지 (0) | 2013.03.17 |