Market has added device compatibility check.Now we can check if an app will work on specific device, for exaple HTC mobile phone, Samsung Galaxy, etc.
What about developer's side: How can we build apps for specific devices only or restrict app for tablets only? How to do restriction in XML and code? It's probably some attribute in Manifest file.
Thanks
Here "Specifying Your Application's System API Requirements" ?
It seems that Market checks this out by itself.
Related
I am reading on the internet, that responsive email templates are supported since Android version 2.3. I am the owner of a Samsung Galaxy Advance, which runs Android 2.3.6. This device sadly doesn't seem to support any kind of CSS at all in a mail template.
Does anyone know if there's a setting which must be turned on? I've tried the nave Gmail and Email apps, but neither of them show emails the way they show on an iPhone for example.
If there's a solution for it, I'd like to hear it.
Thanks in advance :)
Gmail doesn't support media queries. Try reading on your native email app via a different domain. (hook up you#somewheredifferent.com) I had issues with my work email - the corporate Microsoft Exchange (or some security software they have) was stripping the media queries out. When sending to me#myownsite.com it came through perfectly.
Yes, if there is no style tag, then media queries won't be applied. And that is the case with gmail and with some other e-mail clients. If you build the mobile version first and create the media queries to recreate the desktop version, then it will be cool on every mobile devices.
The drawback of this is when you open the mail on a desktop client, which does not support the style tag (so the media queries) then you will see the mobile version on desktop.
If you are looking for a template which does the work for you, then I recomment Antwort. This is a three column layout, working in a way what I mentioned before. (http://internations.github.io/antwort/)
If you are looking for a tool, then I recomment you this: www.edmdesigner.com - although the beta phase has not started yet.
This question has been asked before, but not this year - there is no concrete consensus and I know this is a hot topic. In addition, technology changes rather quickly, and the other questions seem to relate to only using the <input type="file>. I am looking for a more verbose modern way to handle these requests. Although I have been developing in ASP.NET C# MVC3, I have been looking into weather ASP.NET MVC4 Mobile will support mobile file upload. From what I have read, it does not, or it has not been covered in the new release notes.
http://www.asp.net/vnext/overview/whitepapers/whats-new
http://www.asp.net/mvc/tutorials/mvc-4/aspnet-mvc-4-mobile-features
From the research I have done jQuery-Mobile seems rather gimmicky.
http://www.parorrey.com/blog/jquery-mobile/file-input-field-uploading-using-jquery-mobile-framework-form-submission-with-ajax-disabled/
http://forum.jquery.com/topic/jquery-mobile-seems-to-clobber-ability-to-upload-files-via-forms
An example that was posted did not work on my iPhone, as the <input type="file" still existed and was therefore grayed out as inaccessible.
http://filamentgroup.com/examples/jquery-custom-file-input/
Another suggestion I have come across involves forcing the user to email the photo to a user-specific email which doesn't really appeal to me or the customers I deal with - this approach also seems like it could be vulnerable to security breaches.
IS there a way to do this that I have overlooked? How can I show a file dialog on a mobile device?
The Safari browser does not support file uploads. You can see this by visiting many of the mobile sites in the actual browser BUT the actual apps will allow this.
So if you are making a mobile web app that you wish to deploy as a native app, you can use phonegap as a layer to do this.
http://docs.phonegap.com/en/1.4.1/phonegap_file_file.md.html#FileTransfer
Also, it is supported in:
Android
BlackBerry WebWorks (OS 5.0 and higher)
iOS
Windows Phone 7 ( Mango )
I use jquery mobile in a production app and it works just fine. I don't do file upload with it; however, that isn't jquery mobile's job anyhow. JqueryUI has issues with its dialog and file upload as well. There are a number of scripts that help with that. I use ajaxfileupload: http://www.phpletter.com/Our-Projects/AjaxFileUpload/ there are better ones out there now though.
I digress. As far as mobile is concerned it is more useful to have camera features involved rather than pure fileupload. No one knows where they store things on their phones, which is part of the problem. For that case you may want to try phonegap. Try this: http://wiki.phonegap.com/w/page/18270855/Image%20Upload%20using%20JQuery%20and%20Python
Yes we can upload picture through mobile,
Face book is a live example for this.
It works for me on Android.
You can see how facebook does it here: https://m.facebook.com/home.php?refsrc=http%3A%2F%2Fm.facebook.com%2F&refid=8&_rdr
<input type="file" name="file1" data-sigil="photo-input" />
Try going to www.tinypic.com and uploading a photo. I can test on iPhone tonight.
This works fine on Android 2.2+. You can upload photos from your gallery or use the camera to take a new picture for uploading. Any other apps that expose similar behaviour like sound recorders, the camcorder and music apps will typically offer alternatives. If you have a good filesystem app installed this will normally allow you to upload arbitrary files.
On iOS, you have to use an app to upload files. Since this is such a glaring omission in this age of web apps, it is very likely this feature will be added in the next major release of iOS although that is likely a few months away still.
Try this:
<input type="file" accept="image/*;capture=camera">
This should be supported in most mobile browsers and should offer the user a chance to choose a local file (image) or one some modern devices even allow them to capture one in the process.
Hope this helps!
Use Phonegap to bridge the gap between client side libraries and native applications. While the client side libraries give a good handle and easy way to set UI things up, you can use the capability of phonegap to perform device specific operations like camera, scanning, call etc.
Mobile browsers in Android (pre 2.2 it seems) and iOS do not allow file system access. And when it does on Android 2.2+ it isn't full access - it is filtered via apps that hit the FS like Gallery or Music.
I have no up to date mobile phone personally, and we don't have any in our team to allow us to test mobile versions of our ASP.Net websites.
We have now been asked to provide a mobile version of our website (which is a fairly busy site) but I have no means to check the mobile pages.
Any suggestions? Are there emulators or would it better to have the real thing?
It's always better to have the real thing, but if that's not an option, I have used a plugin for FireFox called "User Agent Switcher"
Another route you could go is to get the Android SDK and load up an emulator. It runs a full version of android, so you could open the browser from there (You could also change screen size/device type) - a little more heavy than the first solution, but potentially another route worth exploring.
You can use simulators/emulators - Android, iPhone etc.
Well Apple provide an iOS emulator, which you can download in the developers section of Apple's own website.
Outside of that, the only other testing environment I'm aware of is Ripple, which is a plugin for Chrome, designed to emulate a range of mobile devices. You can find that at: http://ripple.tinyhippos.com/.
As others have answered there is a lot of different tools to do the testing and that is all fine to a certain extent, for daily testing by developers and testers.
But with 15 years of testing behind me I would never let the site go untested with a few different real devices if the site is an important service - usually this can be done with "staff" phones at no cost if the cost is the problem. I would more or less say; can your company live with publishing a site out there and there might be a risk it won't work on some mobile platforms?
DeviceAnywhere is the tool that we have used a lot. It provides you access to numerous mobile devices using which you can test both apps and websites. They have placed several physical devices which you can see and operate remotely.
It is always better to test on real devices instead of emulators. During development phase, emulators are helpful but for final delivery it is best to test on real phones. Mobile web browsers may or may not support HTML,CSS,JS completely and their individual implementation could be different.
My web app is written in Java with front-end in JS. I want to port to tablet and other touch mobile devices. Developing a native API is ofcourse an option but I would prefer making the old app work on tablet.
I know I would need to make some changes in UI for the touch interface and I am willing to do it.
So My question is: A*re there tablet Simulators available on which I can try my app and see where it breaks on such device.*
What would be the best approach to proceed on this?
thanks in advance!
Tablets use various OS's and, thus, different API's, supported features, etc... For iPad, for imstance, XCode provides a simulator. I read somewhere that the BB tablet coming out will have a simulator for dev as well.
Nexus One is not currently supported by the Mobile Device Browser File, which leads to the Nexus One being identified as a non mobile device.
I know the user agent, and the capabilities are pretty similar to other Android terminals. With this information, how do I patch the MDBF to have the N1 be recognized as a mobile device?
Regarding Mobile Device Browser File:
Quote: "Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010."
not sure if it is helpful to you but you can check for Nexus in the user agent field returned by the browser.