기본 콘텐츠로 건너뛰기

[jquery vs sencha touch]PhoneGap and jQuery Mobile vs. Sencha Touch

source: http://brianshim.com/webtricks/phonegap-and-jquery-mobile/

PhoneGap and jQuery Mobile vs. Sencha Touch

PhoneGap Build lets web developers create native mobile apps for iOS and Android without learning Objective C or Java, while still being able to access native hardware features like vibration, accelerometer, camera, and so forth.  This is great if you are a web developer and need to develop a native mobile app on multiple platforms (iOS, Android, etc.)
I was fortunate enough to be able to attend Web Unleashed 2012, a two-day “Front End Developer Event” near Boston, where they discussed mobile app development. One of the highlights for me was a presentation called “Building Multiplatform Apps with HTML & JavaScript Using PhoneGap Build”, by Brian Rinaldi from Adobe.

PhoneGap Build Makes it Easier

PhoneGap Build is Adobe’s attempt to take care of more of the development process for you (especially the convoluted iOS compilation process). In fact, using PhoneGap Build, you can develop iOS apps using a Windows PC! (Apple’s iOS development tools only run on Mac).  Adobe accomplishes this by moving the iOS-specific parts of the PhoneGap development process to their servers on the web, so you only need to upload files there and push a button. To load your app onto your mobile device, you scan a QR code from your phone and it sends you to a link where the files are waiting for you. I went through most of the process and it was relatively painless! The only reason I didn’t go all the way was that I had an iPhone and I didn’t have an Apple developer license ($99), which is required for iOS development.
Android development (and Blackberry, for those who care), works the same way, except that you don’t need a license. If I had an Android phone, I would have been able to run the demo on my phone that day.
I had attended a native iOS development workshop once before, and the whole process turned me off. If I had to develop an iOS app, I’d definitely use PhoneGap Build instead. I’d recommend it to any web developer who wants or needs to develop a native mobile app. This is the easiest way that I’ve found.
PhoneGap Build is free for one app and $10/month for 25 apps. You can find out more about PhoneGap Build here: http://build.phonegap.com/

PhoneGap vs. PhoneGap Build

I wasn’t aware of this before I went, but there is a distinction between “PhoneGap Build” and “PhoneGap” (without the “Build”). Both allow you to develop native mobile apps using HTML, CSS, and JavaScript and give you access to native hardware features. However, PhoneGaprequires that you have a Mac running XCode if you want to develop an iPhone app. That is why Phone Gap Build is so cool – no Mac required. The Mac-specific stuff is done on Adobe’s servers.

jQuery Mobile vs. Sencha Touch

Closely related to Phone Gap is jQuery Mobile, a JavaScript UI framework that gives your app the look and feel of a native app by providing cosmetic elements like buttons, menus, etc., as well as animations like transitions. These elements are not just icing on the cake; Apple requires that native apps have a specific look and feel, so you’ll either have to craft these elements yourself or rely on a framework.
I have previously used jQTouch for this, which was easy to use, but doesn’t seem to have much momentum behind it now. For my next project, I’ll definitely use jQuery Mobile. It seems very easy to use for anyone familiar with HTML and CSS and it appears to be well-supported by Adobe.  More on jQuery Mobile here: http://jquerymobile.com/.
I also attended a talk on Sencha Touch, which is another mobile app framework, but is a much bigger departure from traditional web design methodology. With Sencha Touch, the whole HTML body section is generated dynamically by the JavaScript framework, in a more MVC philosophy. You don’t write any HTML code for the body directly, which might be disconcerting to some developers. I think most front-end web developers would feel much more at home with a less radical framework like jQuery Mobile. I know that if I needed to develop a mobile web app fast, I’d be up and running much quicker with jQuery Mobile than Sencha Touch.  Pure JavaScript programmers, on the other hand, might prefer Sencha Touch.

A Side Note: The Brackets Code Editor

Some of the coolest things I discover from these presentations are the tools that the presenter uses.
Brackets is an open-source code editor created and maintained by Adobe. One of the coolest features of Brackets is inline code editing.  Say you are editing a div tag in your code and want to see the CSS that goes with it.  Click a button, and the CSS for that div appears right below the line you are editing.  Very cool!!!
Brackets is still in beta, but I’m going to be watching it.  It could become the code editor that you’ve been looking for too.

Mongoose: An Easy-To-Use Web Server

To get people who didn’t have servers running on their laptops up and running quickly for the workshop, the presenter recommended usingMongoose. You simply download it (it works on Mac or PC), copy it to a directory, launch it, and boom, you have a web server running on your computer. No messing around with installing WAMP, MAMP or XAMPP. I already had a web server running on my laptop, but this seemed pretty cool.

The Verdict

If you are a front-end developer accustomed to building websites with HTML, CSS, and some JavaScript, you will find jQuery Mobile to be definitely easier and quicker to develop with than Sencha Touch.  If, on the other hand, you are a professional JavaScript programmer who likes the “MVC way” of doing things, you’ll like Sencha Touch.  As for Phone Gap Build, I’d recommend that for anyone who hasn’t already gone through the painful iOS development process.  Save yourself some headaches!
Have you used Phone Gap or PhoneGap Build? What are your thoughts?
- Brian

댓글

이 블로그의 인기 게시물

[linux] 뻔하지 않은 파일 퍼미션(file permissions) 끄적임. 정말 속속들이 아니?

1. [특수w]내 명의의 디렉토리라면 제아무리 루트가 만든 파일에 rwxrwxrwx 퍼미션이라 할지라도 맘대로 지울 수 있다. 즉 내 폴더안의 파일은 뭐든 지울 수 있다. 2. [일반rx]하지만 읽기와 쓰기는 other의 권한을 따른다. 3.[일반rwx]단 남의 계정 폴더는 그 폴더의 퍼미션을 따른다. 4.[일반]만약 굳이 sudo로 내 소유로 파일을 넣어놓더라도 달라지는건 없고, 단지 그 폴더의 other퍼미션에 write권한이 있으면 파일을 만들고 삭제할 수 있다. 5.디렉토리의 r권한은 내부의 파일이름 정도만 볼 수있다. 하지만 ls 명령의 경우 소유자, 그룹, 파일크기 등의 정보를 보는 명령어므로 정상적인 실행은 불가능하고, 부분적으로 실행됨. frank@localhost:/export/frankdir$ ls rootdir/ ls: cannot access rootdir/root: 허가 거부 ls: cannot access rootdir/fa: 허가 거부 fa  root #이처럼 속한 파일(폴더)만 딸랑 보여준다. frank@localhost:/export/frankdir$ ls -al rootdir/ # al옵션이 모두 물음표 처리된다.. ls: cannot access rootdir/root: 허가 거부 ls: cannot access rootdir/..: 허가 거부 ls: cannot access rootdir/.: 허가 거부 ls: cannot access rootdir/fa: 허가 거부 합계 0 d????????? ? ? ? ?             ? . d????????? ? ? ? ?             ? .. -????????? ? ? ? ?             ? fa -????????? ? ? ? ?     ...

[인코딩] MS949부터 유니코드까지

UHC = Unified Hangul Code = 통합형 한글 코드 = ks_c_5601-1987 이는 MS사가 기존 한글 2,350자밖에 지원하지 않던 KS X 1001이라는 한국 산업 표준 문자세트를 확장해 만든 것으로, 원래 문자세트의 기존 내용은 보존한 상태로 앞뒤에 부족한 부분을 채워넣었다. (따라서 KS X 1001에 대한 하위 호환성을 가짐) 그럼, cp949는 무엇일까? cp949는 본래 코드 페이지(code page)라는 뜻이라 문자세트라 생각하기 십상이지만, 실제로는 인코딩 방식이다. 즉, MS사가 만든 "확장 완성형 한글 ( 공식명칭 ks_c_5601-1987 ) "이라는 문자세트를 인코딩하는 MS사 만의 방식인 셈이다. cp949 인코딩은 표준 인코딩이 아니라, 인터넷 상의 문자 송수신에 사용되지는 않는다. 하지만, "확장 완성형 한글" 자체가 "완성형 한글"에 대한 하위 호환성을 고려해 고안됐듯, cp949는 euc-kr에 대해 (하위) 호환성을 가진다. 즉 cp949는 euc-kr을 포괄한다. 따라서, 윈도우즈에서 작성되어 cp949로 인코딩 되어있는 한글 문서들(txt, jsp 등등)은 사실, euc-kr 인코딩 방식으로 인터넷 전송이 가능하다. 아니, euc-kr로 전송해야만 한다.(UTF-8 인코딩도 있는데 이것은 엄밀히 말해서 한국어 인코딩은 아니고 전세계의 모든 문자들을 한꺼번에 인코딩하는 것이므로 euc-kr이 한국어 문자세트를 인코딩할 수 있는 유일한 방식임은 변하지 않는 사실이다.) 물론 이를 받아보는 사람도 euc-kr로 디코딩을 해야만 문자가 깨지지 않을 것이다. KS X 1001을 인코딩하는 표준 방식은 euc-kr이며 인터넷 상에서 사용 가능하며, 또한 인터넷상에서 문자를 송수신할때만 사용.(로컬하드에 저장하는데 사용하는 인코딩방식으로는 쓰이지 않는 듯하나, *nix계열의 운영체제에서는 LANG을 euc-kr로 설정 가능하기도 한걸...

[javascript, 자바스크립트] 버튼을 a태그처럼, a태그를 버튼처럼

사실 첫번째 submit은 버튼이지만 css style로 hyperlink처럼 바꾼 모습이고, 두번째 submit버튼모양은 사실 hyperlink지만 css style로 버튼마냥 바꾼 모습니다. 적용에 사용된 소스는 아래: <!DOCTYPE html> <html> <head> <style>     a.button {       -webkit-appearance: button;       -moz-appearance: button;       appearance: button;     }     input.submitLink {     background-color: transparent;     text-decoration: underline;     border: none;     cursor: pointer;     } </style> <script>     function formSubmit()     {     document.getElementById("frm1").submit();     } </script> </head> <body> <form action="test1.jsp" method="get"> name: <input type=text name="name"> phone: <input type=text name="phone"> <input type=submit value="subm...