Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
What JavaScript Mobile development tool would you use based on momentum, existing documentation and functionality, and ability to get passed the App Stores strict policies?
Current PhoneGap release (0.8.0) released 2009-10-13 is tagged "Apple approved for App Store submissions". This blog post has more details.
I used PhoneGap to port a JavaScript game and I loved it. Unfortunately, the game was too slow (Mobile Safari is slow when you make changes to the DOM, and I was moving divs around as sprites) and I switched to native.
But since some people started getting having their PhoneGap apps rejected, I have become shy of the project. I'd love to hear an official stance from Apple, but I don't know if it'll ever come.
I found Phonegap to be the easiest to use. However Quickconnect seems to be more ambitious in terms of multi-platform support, the author tells me that Quickconnect has been used in many apps (but couldn't disclose which). Supposedly Phonegap apps were being rejected because those submitting were loading the entire apps off the web, however the framework does seem sluggish. Apple has not replied to the Phonegap team about the app rejection.
If I had to make a choice it would be Phonegap at this stage, but unless you really want the app on multiple platforms I don't see why you wouldn't use the great tools provided by Apple for native development.
At this point you might also want to look at Titanium by Appcelerator.
The development process is pretty simple, and they support both the iPhone and Android platforms.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
With the release of Chrome 77 the Web Serial API became available with the use of an experimental flag. This is particularly useful for desktop applications running in NW.js or Electron, where NodeJS has previously (and still does to a large degree) provided a bridge between web and native.
I find myself very much wanting to abandon the use of NPM packages like serialport, which extend both NW.js and Electron to provide serial port access.
While Electron 8.0.1 does make available navigator.serial, it's not exactly clear how much of the API is actually implemented. To further complicate things, there is no good documentation for the API (at least in my search) besides https://wicg.github.io/serial/ and https://github.com/WICG/serial/blob/gh-pages/EXPLAINER.md. I've tried tinkering with it on my own, but it's not clear whether I'm using it incorrectly, or whether parts simply aren't implemented.
So what is the status of this API? Which parts are reliably implemented (in Chromium), and is there any indication of when this will be ready for prime time? I think a lot of people are wondering this as it opens quite a few doors for interaction with the user's PC.
Here are some resources for tracking the status of the Serial API and its implementation in Chromium,
Draft Specification, as you've pointed out it is incomplete and I'm working on fixing that.
Specification "explainer", this is a less formal introduction to the specification and a more up-to-date reference for the current design of the API.
Chrome Platform Status entry, this tracks the official implementation status in Chrome.
Chromium implementation tracking issue, star this issue for updates as the implementation work progresses.
Polyfill library, this library uses WebUSB to implement the API for standard USB CDC class devices. Think of this at the moment as a prototype of what the API could look like when implemented in a browser.
Code lab, if you're looking for a larger example of how to use the API this code lab explains how to get started communicating with a particular device in a step-by-step fashion.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
After research i made on the web, i found two frameworks: for desktop development - electron and for mobile development - ionic
Are above platforms recommended choices for mobile and desktop development with web technologies? If not which frameworks should we use for this purpose?
There is few technologies regarding to your question. Cordova-PhoneGap-Ionic (they rely on Apache Cordova) applications are running on WebViews. This means there may be performance issues if you use them for some goals, for example hard calculations. By the way you can still use native functions via Cordova Plugins too.
Also there are NativeScript and ReactNative too. With these technologies, your applications are running on native environment. It looks like these technologies are trending now.
You have a bunch of different possibilities, for instance OnsenUI, Kendo, Ionic (1 or 2), etc. I would recommend you to spend a bit of time to understand which one is better for your needs, even though I would say that Ionic is pretty popular now.
This page is a good start to have an overview of a few popular ones with a short review. http://www.gajotres.net/best-html5-mobile-app-frameworks-ionic-review/ Please note that Framework7 is not in the list, but might be worth mentionning (but I feel more iOS oriented).
Your question is specific about HTML, CSS and Javascript. But as a side note, please do not forget that you might have other options as well as suggested above (ReactNative, Xamarin with C#...) You may check: http://noeticforce.com/mobile-app-development-cordova-vs-react-native-vs-xamarin
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Well, perhaps this is silly but I wonder is it possible, to transfer a web app built in Javascript with some html and css to linux platform?
I made a youtube player smth like youtube client, and I want to use on my Ubuntu 15.04 OS, as an app.
Here is a preview:
and I would love it if it would look smth like this:
I know that this Google Mail is just loaded from a web, but I want to make it accessible from my Ubuntu. Just instead of this google I ant that my app gets in. I hope you understand...
As has been pointed out, JavaScript and HTML5 don't "natively" run on Linux -- so you'll have to find an application to wrap yours. Plenty of these things exist -- Electron is very popular, as is nw.js.
Well, I'll try to take a stab at answering your question:
If you want to run it natively on linux without any other application being involved the answer to your question is not without rewriting it to some other language. Linux does not run javascript natively.
If you want something thinner then a web browser perhaps something exists to run your web app for you, but it's essentially going to be a light web browser. If you want to run javascript there will always be some other application between you and the kernel unless the kernel specifically supports javascript which Linux does not (and AFAIK no kernel does).
So in short, based on what I think you're asking for, no.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
What are the necessary things for creating card game on iPhone??
The purpose of this app is to share the ideas by using cards.
Each player will draw a card and do what the cards order to do such as write the comments on those topics and so on.
I'm quite new for the programing. I don't want to learn Objective-C. It is quite hard for me.
I have searched on google that PhoneGab can port HTML5,CSS&JavaScript to be an iPhone app.
So the things that I must learn are HTML5,CSS & JavaScript only?
This app must have many players to play for sharing the ideas. Therefore, must I learn other programing languages? such as, php.. to manage each player data (profile).
Moreover, I would like to use points, badges, leader board in this app, too
How about and SDK or any software to help me write code easier?
(p.s. Sorry for my bad English)
That's a great idea!
You will probably have to learn all that languages and depending on the things you want php will be included...
My advice: if you are new on programming and will have to study a while, I say it is better to do a native iPhone app. A web app will have tons of things you will have to worry about so the app can run on different devices... So, will be more complicated to deal with that kind of stuff than learn and develop a native iPhone app...
Including that you want to use features like badges and leaderboards, all native on each device, so you don't have to worry on creating something from zero, like in a web app...
I hope it helped!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am developing an application that will be running on different mobile OSs, so I would definetely use phoneGap Build as a cross-mobile building tool. But my question is, why should I then use phonegap.js (the library) at all? Does its API includes features that I cannot reproduce with javascript libs?
If you don't need sensors or actors (camera, microphone, etc.) from the device you don't need it. If you do, you should use it.
Yes. In a nutshell, PhoneGap will give you acces to certain platform-specific features that wouldn't normally be available to a web app.
See PhoneGap's feature list to see what you may gain. Note, though, that some (not all) of these features are also now supported by modern HTML5-compatible browsers.
It's a pretty sophisticated API. You should definitely at least explore what it exposes. Especially when it comes to anything involving the camera, it includes a lot of great methods.