What i wanted to know is if i develop a single metro style app using html5 and javascript can d same app be used for iphone and ipad as well?
Can anybody help me out with this?
I believe you can create an app with pure JavaScript+HTML5+CSS3 which should work cross-platforms (to the degree of web standards support in browsers). You would need to package the app differently for different platforms or just host it like a website, but it should work. The problem is - usually when you develop Metro style apps for Windows 8 - you use WinJS APIs or general WinRT APIs to interface with the OS, which would not work cross-plaforms, so it really depends on how complicated your app is, how much effort you want to put in the development and is it really the right choice to have it look the same on all platforms. A Metro-style app could look a bit out of place on iOS or Android devices and vice-versa (although you could argue Metro style looks great everywhere and should be the easiest to port), while if you try to create something that works everywhere - you might end up with something as ugly as desktop Java apps were historically. Doing a shared cross-platform design might be counterproductive and countereffective.
Related
All my searches have turned up nothing of use. I saw mention of UTM but you have to do some shady stuff to get that to work and Merge VM Pro but that only has 5 reviews and 2 say it is a pile of junk.
I can't find any container frameworks that run on iPad.
Most search results are people saying Apple won't let other operating systems run on their devices which certainly fits Apple approach.
Any other legit ideas are appreciated. Basically I have an existing MVC Web app but I need it to work when iPad has no connectivity so can't use it like it is intended with just going to it from a Web Browser. It is a pretty beefy app so rewriting it in some other tech to run on iPad (e.g. Swift, Xamarin, HTML5) is what I am trying to avoid.
I am new to mobile programming, and I want to build a mobile app to fill few forms, offline, and then sync them later, when internet access is available, with a database on an online server through a VPN connection.
At first, I thought about learning Windows8 Phone App development, but then I heard/read about Phonegap and Jquery Mobile! and I am a bit confused which one would be better to use, considering two things:
1- Which one you think would be good for my app's functionality
2- Which tool would be more beneficial on the long run (in the mobile programming world).
Any advice would be very much appreciated.
With these functionality I don't thing you don't need many mobile dependent features rather you need more web features. For your first question, answer could be that technology in which you are more comfortable. But it also depends how you want to sync your data. In background or when the app is open. If you want to sync data in background that means app is closed, you have some data to send in server, and internet access is there, then you'll need some native windows phone code. In that case if you use phonegap ultimately you will need some native code to deal with it, may be you'll need to write a plugin to communicate between phonegap and native code. And if you don't need background process, if you want to send data to server only when your app is opened,phonegap can work like a charm. It'll be easy to communicate between 2 web technology.
For your second question, ofcourse phonegap is great technology to learn to deal with cross platform. If you need to make apps not only for WP rather for all platforms then phonegap is great. Having said that it's necessary to mention phonegap has it's quirks too. Native code always has it's benefit. Phonegap can't completely overcome native code. But if you are willing to compromise a bit, then it's easy to learn phonegap,a familiar tech than all those platform dependent techs like objective-c, android etc.
(N.B. I'm not an expert, it's just my experience so far)
I have made my first app in the Android platform. However this is not the only platform and I want to get my apps published on at least Android and iOS platforms.
I would like to have one developing platform for both platforms. What is the options?
I have now tried Flex, Air with Flash Builder. It seems quite promising but the future seems to be a bit uncertain and are also more expansive.
It would be interesting to have some suggestions about what developing tools to focus on if I would like to develop apps on both Android and iOS.
It depends what kind of apps you want to build (i.e. Games, Content Aggregators, etc.) because each 3rd party "App-Generator" that deploys to multiple platforms has their strengths and weaknesses.
Here's a (brief) list:
Appcelerator's Titanium SDK - leverages mobile-browser-based features, mostly for content-aggregators, simple or core feature list on platforms
Corona - leverages LUA-scripting language for 2d / more simple games and applications; has a growing user-base and community; possible to leverage for core-experience as well
Unity - 3d experience, games, usually for more high-end, premium experiences
If you're going to develop on the platform, I always recommend build to that platform's language since you'll never have to worry about what happens when the language is upgraded and your "app-generator" hasn't upgraded yet.
It will also help you to learn the language on that platform (Java, C#, Objective-C, etc.)
I know it's old topic but for those who are still looking for rapid mobile development there is also Kinetise that is code-less tool and offers also backend system/CMS.
You can use Sybase Unwired Platform. It has Device App Designer which can create applications for Blackberry ,Android and iOS.
If you are aiming for high quality, I don't think there is any other way than going native for each platform. Also keep in mind that different platforms have different UI guidelines and principles, and doing a multiplatform project is not a good enough reason to abandon those guidelines.
I recommend phonegap: http://www.phonegap.com
This is kind of a dumb question but I've aware of classic style JDE development for Blackberry but I've never tried using WebWorks. BB website says that it's possible to build applications for both smartphones (OS 6.0+) and tablets - sounds fantastic, but what's the price?
Is here anyone using WebWorks on a daily basis and capable of describing pros and cons?
Thanks in advance
I would suggest using it if you build webOS applications before hand. It make porting to the blackberry a breeze.
Use WebWorks if you know html5, Css3 and javascript over Java and C++.
I haven't ran into any issues with the webWorks, ported two applications without running into any issues. Its your standard html5, css3 and javascript you love with blackberry APIs
WebWorks is a good development choice, particularly as it allows easy migration from earlier BB OSes to BB10. It's mostly standard web technologies (HTML5, CSS3, etc.) and the team seems focused on making it perform well (e.g. hardware accelerated WebGL graphics) while at the same time providing BlackBerry-specific APIs to make WebWork apps capable and with good UX (e.g. you can make it look like a native app).
For native apps, you should look into Cascades. This is a modern development environment with good tooling, accelerated graphics, and APIs for building snazzy apps. It's the one that will most be a "BlackBerry app".
AIR remains an option, but I would recommend WebWorks over AIR, as even Adobe is migrating from Flash to web technologies. Likewise, you can develop Android apps on BB10, but unless you are keen on Java programming, you will get more cross-platform support from WebWorks (or even AIR) so there's no particular reason to go the Android route.
WebWorks API is limited, for example it does not have socket, so you cannot port a VNC (UltaVNC, tightVNC ..) to it but you can do it with JDE.
For UI, WebWorks allowed me to write UI of acceptable quality quickly and easily, a thing that I have never succeeded with JDE.
Still on the UI side, I can make use of multi-touch (PlayBook), I don't think this one is possible with JDE.
So depending on your needs you should go either WebWorks or Native, having heard that Java may not be supported in BB10, and Air may not be future proof (Adobe favors HTML5 instead of Flash). Android appli has some lag on start up when it is run on PlayBook, some customers are sensitive to the initial even just one time slow response time.
I'm a huge proponent of Webworks. Ever since I've started using it, it quickly became the default option for my apps going forward. Especially for someone like me who is just writing a few apps on the side, I don't have the time to do it in c++.
The apps I'm writing revolve around home automation. They are client/server based from the get go.
Here's why I like it:
First and foremost, native API support. I can very easily create my own active frames, import invocation from other apps (think camera, stuff like that). I can export portions of my webworks app as an invocation card! Which means I can write say 3 unique apps (in this case home automation, lights, thermostat, security cameras). And I can very easily pull features from each app into the other. Maybe I want to turn my lights on in the living room, I can also import the camera card from my IPcam app and view the results, without having to add that code into my lights app and maintain two separate code lines.
Rapid design. Since I've been dabbling in html since I was a kid, it's now very easy for me to whip up an appealing UI in little time. Because web engines these days offer good performance in terms of graphics capability, I also can make apps that behave very fluid.
Considering the time to make something beautiful, it's hard for me to leave webworks and go for something in c++. Also the big plus is often these apps I'm making are intended for multiple devices, namely an app on my phone and being hosted on my personal website. By maintaining two slightly different css files, most of the time I need no code changes, just load a different css depending on if it's a phone or a pc. (Exactly what you'd do if you were developing a regular old website).
For that matter, I actually don't put my code on the device, I host all of my html and javascript, images etc on my server. The webworks app is just the config.xml pointing it's source to my server, and an icon. A glorified website bookmark on the homescreen, only difference is I can use native API and there's no browser bar in the app.
Also, this way I can still continue to edit the same single codeline on my server, and instantly apply changes to the in-browser app and the on-device app.
This is especially cool if you're designing an app where all of it's data is out in the "cloud", say you work for a publication and you want to write a magazine app which pulls content from your servers on the net.
Could someone provide a good link to book about how to develop iPhone application with the Perl programming language?
Why would you want to use Perl? You'd miss out on everything the iPhone SDK gives you, and you wouldn't be in the iTunes App Store.
If you are trying to use Perl because it's the only language you know, just bite the bullet and learn Objective-C. Use the right tool for the right job. Despite how much I enjoy working in Perl, I don't think it's the answer to every problem.
However, if you did want to use the Perl route, you could use it to drive an HTML-based app. You end up installing a mini-website with local storage, etc, on the iPhone. Building iPhone Apps with HTML, CSS, and JavaScript is in O'Reilly's Open Feedback Publishing System, so you could see how to do that for free. Perl might be a tiny, server-side component of that.
Generally Perl is not a good choice here. Without jailbreaking the iPhone, you will need to compile perl into a static library and link it against your byte-compiled code (or build a small app that glues the two together). This seems a lot of work for little benefit, since Perl has no bindings to the various Cocoa and UI elements you'll need to manage your run loop. Why do you want to use perl here?
Jailbroken development is outside the license agreement. Searching "perl iphone" will give you several links on the subject, but I really can't go much further into that.
If you insist on Perl, relax your constraint on it being an iPhone "application". Make it a web application targeted for the iPhone!
Pros
You can use all the Perl you want! Even Catalyst!
Any version of Perl you want, in your own configuration.
Cross platform with other mobile/Internet devices.
Way easier to deploy updates and bugfixes.
Cons
Requires a constant internet connection.
Is accessible outside of the iPhone enviroment.
Isn't in the iTunes store.
Tradition breaker.
If you mean backend to a iPhone application (via XMLRPC), then we are all behind you I believe.
I think Perl is a fine choice for writing a web based mobile app.
mate it with one of these tools for creating a native look and feel for a variety of mobile platforms:
http://code.google.com/p/iui/
http://www.phonegap.com/
http://www.jqtouch.com/
my 2 award winning iPhone mashups run on Perl :)
http://imoviemash.com
http://imusicmash.com
Al