iOS enterprise apps has the ability to be distributed over the web using a manifest file. Can the tvOS be distributed in a similar manner? I know there's no web browser for tvOS, but I was wondering if there's a way to airdrop a file onto the Apple TV to install an internal tvOS app?
The only way so far is to either use an MDM server or use Apple Configurator via a Mac to drag and drop an IPA.
You can use Testflight to distribute you App in-house creating a group of internal or even external testers.
Sadly HockeyApp or similar 3rd party distribution systems do not support tvOS yet.
We are planing to develop new app .It has VoIP feature and app is similar to whatsapp.
Since the app has Voip feature we have to go with WP8 silver light. Winrt for WP is not supporting VOIP api.
Can we guess almost all the WP8 devices are upgraded to WP8.1 ? If there are large user base still remains in WP8 we will develop the app using WP8 api's (Using VS2012). Otherwise we will go with WP8.1 api's (using VS2013).I heard there are few performance improvements and controls are available in WP8.1
Any suggestions on this ?
Thanks in advance
All Lumia phones can be updated to WP8.1 and a huge part of users so did.
Just an article for reference: http://www.engadget.com/2014/04/02/nokia-lumia-windows-phone-8-1-update/
On my apps I use analytics to track users and I hardly see few users stuck with WP8.
Update - market share
http://www.gsmarena.com/adduplex_wp81_market_share_surpasses_wp80-news-10062.php
This article is from last October, WP8.1 has been out for about 5 months and it had already surpassed WP8. I let you think the actual quota...
Should you go with WinRT? It depends on your needs. Of course you should use at least WP8.1 Silveright (not WP8). But if your application does not require specific functions only available in WinRT, you might go with WP8.1 Silverlight, since WinRT has still many little performance issues.
There are a lot of new available APIs and features either for WP 8.1 Silverlight or WinRT. I would definitely target 8.1. Users still using WP 8.0 probably don't care that much about apps anyway.
I have a virtual world (user login, create avatar, walk around and play games) running on web with flash/as3 as client side and smartfox2X as server. I have plan to get the whole system into android tablets.
My question is How do I achieve this? or what is the best way to convert the same to run on tabs.. Will the just changing in publish settings from flash player 11 to Air for android work ???
Will the just changing in publish settings from flash player 11 to Air
for android work ???
Yes, this will work to some extends. You will not be able to run native code or to use native acceleration.
You can take a look at Haxe and OpenFL, which allows you to compile "flash" as Android native app.
I use flash developer and create AIR Mobile AS3 App and I wonder how can I change an app run time from desktop to my mobile device?
Thanks
In flash builder, you have to set the Run/debug configuration, what looks like below:
you have to select the platform (Android, BBRY, etc), and "On device". If you have Android device for example, make sure its connected, and in development mode. It should work,but you'll find lots of help.
I am building an enterprise application using HTML5 for Blackberry OS 6.0. I am planning on using PhoneGap for developing the application. I found out that Blackberry also has something similar called WebWorks.
What are the differences between WebWorks and PhoneGap?
PhoneGap-BlackBerry-Widget uses the BlackBerry Widget SDK to support BlackBerry OS 5.0 & 6.0. WebWorks is basically Widget SDK 2.0 and it is intended to support OS 6.0 specific features.
The advantage of using PhoneGap-BlackBerry-Widget over WebWorks is that you can port your application to other platforms that are supported by PhoneGap.
You can still port an application that was written using WebWorks/Widget SDK, but you will need to switch out the BlackBerry-specific JavaScript bindings for the PhoneGap JavaScript bindings (e.g. invoking Geolocation, contacts, or accelerometer).
Looks like WebWorks is specifically for BlackBerry while PhoneGap is attempting to support multiple mobile platforms.
I haven't looked too deeply into WebWorks, it appears to be more tightly integrated with a specific device, a Blackberry
WebWorks is a specific development tool managed by RIM for BlackBerry, while PhoneGap is in the MEAP (mobile enterprise application platform) space where they represent the next generation of mobile development. You develop your app with PhoneGap and it helps you to deploy across all major platforms such as iPhone, Android, Windows Mobile and BlackBerry. If you're a developer then it opens the doors to more phone models and increased opportunity for app sales.
webwork vs phonegap
both are used for build application .using webwork u get for feature for specially blackberry....using phonegap u can use same code for multipal phone like iphone,android..
but i prefer webwork because phonegap add unwanted code to your applicatio due to application very slow ....phonegap + wework in blackberry 5.0 take too much load...it's min size is around 600 kb......
so for blackberry webwork is better than phonegap
One issue to consider is testing and compiling applications.
When testing on devices and simulators it is possible to compile/sign once and access/edit your JavaScript and HTML5 from a remote location, such as the SD Card or a local server. While PhoneGap and WebWorks are both using JavaScript to access native functions, I have found the 'compile once' method doesn't seem to pick up and utilise PhoneGap - this is also the case with the Ripple emulator. In my experience, using PhoneGap requires multiple, time-consuming compilations and launches when testing an application. If testing on a Blackberry device, you need to factor in the time it takes to have your app signed prior to each test and the time it takes for the device to reboot. I'm talking 2+ mins on a simulator or 4+ mins on a device, per each change to your code.
I'm working with webworks for Blackberry and phonegap for iPhone. Not sure whether the problem is with webworks or underpowered handsets but we've had to spend a lot of time ripping features out of the webworks app to get any kind of robustness or performance when running on the device. Static google maps and thumbnail photos had to go.
All webworks apps on a handset share the same pool of memory, about half of the memory available to the BB browser. Webworks also leaks memory. There's a thread a year old on the webworks forum about the memory leaks and no solution forthcoming from Blackberry, just "workarounds". We had to alter the webworks sdk to make the garbage collection more aggressive to stop the app running out of memory all the time. But if other webworks apps are running on the handset and haven't had this GC tweak you will still get grief with memory.
Don't know if phonegap is any better than this but it'd have to go some to be worse than webworks.
If you want to do a webworks app keep the design simple, package all the graphics and assets in the deliverable (we were trying to get icons from an api but have ended up storing them base64 encoded in localStorage) and get it onto a handset asap so you don't waste time adding features that the handset can't cope with.
To sum up, webworks is pretty poor.
PhoneGap : is an application with a webview control that renders your HTML5 and JS. PhoneGap has diferent versions or say release for different platforms like Android, iOS, BB, WP8 etc.
WebWroks : is conceptually the same thing as PhoneGap just that it is owned and developed by Blackberry (Previously RIM) themselves.
Also one most important thing in the context of the question is that, for Blackberry Phonegap uses WebWorks as its base, that is why while developing PhoneGap Apps for blackberry you need to download WebWorks SDK first, the build process is also the same as WebWorks so the benefit of using Phonegap for balckberry is that the same HTML5 + JS Code that you used for say Android will work on Blackberry as well.
However BB OS 7 and below do not have the best WebView Control, BB 10 and playbook are MUCH MUCH Better.