Does anyone know of an easy way to present an android app through a website? Maybe the equivalent of an emulator running on a webpage. It would be great for demonstrating app functionality via the web and doing basic initial customer design approval without them having to install an app. It would also be good for marketing existing apps.
I think creating a video is the best way. If you are on a mac, try this:
Screenflow
If you are on Windows, try this:
Camtasia
I use ScreenFlow and then put the video on my website for clients to see.
You can use Droid VNC Server on your own handset and connect an android handset to your Network, then give them a webpage with the HTML web viewer of Droid VNC server. That would probably give you the best solution and would be transparent for the customer.
Do this
Install the ADB Driver to directly debug the app in Android Phone
Open Android Studio, directly run your app in Android phone.
Click the Capture icon. its capture the screenshot of android phone.
4.See the images , Android Studio have own Screenshoter, Video Recorder.
5.No Need of Third party Softwares.
Hope this helpful.
Happy Coding :)
Android being based on Java, I guess one could adapt the emulator for a webbrowser version, but this would be quite long, and inefficient.
If you forced your user to download the emulator (you could package it without the whole sdk), you could make a batch script to launch it and install your apk, but for a lambda user this would be too much trouble to test one app.
The only solutions left are
making a video of your app's features (you could then add subtitles and graphic design to enhance a point in the video)
make a fake version using flash or HTML5 / javascript
make a java applet (you could then reuse some of your code, and only redesign the GUI)
I would recommed using TeamViewer or other simmilar remote access/remote desktop sharing solution.
Teamviewer is free.
ps.
i know this is not on webpage, but i figure if you'll be presenting this could be a good option.
Related
What is the proper way to have an app shell that simply loads a website. and properly handles orientation, etc?
We are releasing our app in a fragmented roll out - We have our mobile website completed, but require a native app to download, we will be swapping the 'guts' of our app in a few months with proper native code, so want to simply open the website up if people download our app for now
I found stuff like this
https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/
I also know that a webview can be used, but is that the proper way to do that?
For iOS, WKWebView is definitely the way to go moving forward after iOS 8.0 with its technology almost similar to Safari's Web View Controller. It is highly customizable and you may want to check out the documentation here to learn more.
I know that those kind of questions have been asked before, but I couldn't find a topic to help me.
I have been give a HTML5 game and I was asked to verify if I can run it on an Android tablet.
I'm a little bit confused with what I have to do? Should I create an Android project and import the file or is there an easier way to create an apk?
Thanks for your help.
You could look at Apache Cordova. This is a powerful environment made to support app development in HTML5. As such you should be able to literally copy your game resources over, run a build and have a full fledge Android App. Fun fact, provided you have access to OS X, Cordova will produce an iOS compatible app too.
If your game consists of HTML, CSS and JavaScript, such that it can be run off a modern web browser with no special plugins installed, rest assured it can run in an Android tablet.
You could access it directly from the tablet's browser or you can make an app (packaged in an APK and installed from it) which does essentially the same, but with a great benefit: the web page and the app can communicate (via JavaScript), enabling a richer experience.
Example of such communication: you're making an app for a web forum, and the link for "compose new message" opens an Android activity for writing that POSTs the result to the server, instead of constraining you to write in a small web browser form.
For more information on the subject, check out Android API Guides for Web Apps.
My goal is to replicate my CouchDB to Android to allow offline access & reduced latency.
I watched this video:
http://www.youtube.com/watch?v=3RdcKWYGqig
One fundamental point I don't get is:
Does CouchDB replication work only
for Android Applications?
Or, can it work for a web application
running in the Android browser (this
is what I am shooting for)? If so, how?
you would need to install the CouchDB software on the Android device in order to get it to work.
Once that is installed, the user can visit your app via the browser at http://localhost:5984/path/to/my/app
You could create one of those bookmarks that looks like an app, and point it to the local couch url.
Chris
Ofcourse you can create browser based applications.
Either try creating a couchapp and loading it with the browserview in android or club it with something like Sencha to wrap it around and making it a hybrid native web app!
If you know how to create couchapps, then it should be pretty straight forward, else, take a look into how to create simple couchapps. Ofcourse, i'm going under the assumption that you already know a bit of Android!
I am new with Android programming and I am investigation the various approaches to built an app. Right now I am learning native app development using Eclipse and ADT but I also wish to look at webviews and their possibilities. Either done directly using Eclipse/ADT or via tools such as PhoneGap.
I know the pros and cons of webviews, but to better learn under what circumstances they are appropriate and likewise where they fail, I would like to analyze various existing apps and check if they are built upon a webview or programmed natively.
The thing is that I sometimes have a feeling that a given app is a webview because the look and feel is a bit different, but on the other hand perhaps the developers simply chose that look for some reason.
So, can I somehow determine if an app is made from a webview?
Try the following option that exist in different phones like S3:
Go to: "setting" -> "Developer options" -> check "show layoutboundaries"
I think that if the app is done native, the boundaries will be displayed for all the objects, while if it is a webview, no boundaries are displayed.
hope that will help...
Without too much trouble, you can look inside the apk and determine if the app uses WebView:
A. find the apk:
Installed apps are on your Android device in the folder /data/app and has domain-style filenames
/system/app has android apks
B1. If the Android device where the apk is installed is rooted, you can explore the apk on the device using for example the app Solid Explorer.
B2. Alternatively, you can enable debug on your Android device and copy the apk to a computer using adb (apks are actually zip archives.)
C. Then for a WebView app:
C1. Inside the apk, in folder assets, there are typically files with .html extension. These are Web pages displayed in the WebView.
C2. Inside the apk, in file /res/layout/main.xml (or perhaps views by other names with .xml extension), the phrase "WebView" is used.
Many slow apps are in fact not WebViews :)
If you have the source code to the app, look at the source code.
If you do not have the source code for the app, see if it has an About menu or something that indicates what they used, or see if the Web site for the app discloses how they wrote it.
I would venture that 95% or more of Android apps are native. Of the remaining 5%, the vast majority that use WebView do so to simply wrap an existing Web site but have it "be an app" for marketing purposes. While PhoneGap is a very slick tool, IMHO only a small percentage of Android apps on the Market use it or similar WebView-based technologies (e.g., Rhodes). That percentage will likely grow over the next few years, particularly as people use PhoneGap to do cross-platform development, or wrap an HTML5 Web app for offline use.
This works for me:
Install & open the app
Uninstall WebView by running adb uninstall com.google.android.webview
If the app closes after uninstalling WebView then it's using WebView
I'm assuming that you have an updated version of WebView and not the stock version that comes pre-installed on the device
To check if WebView has been updated run adb shell dumpsys package com.google.android.webview | grep versionName and there should be two different versions, one is the current version and the other is the stock version.
A certain way (but perhaps more complicated) is to root the device and install a Proxy (like https://play.google.com/store/apps/details?id=org.proxydroid&hl=en). Then you can observe HTTP traffic and try to determine if the app is using a WebView.
I have an app in Android Market which is a standalone app that's essentially a full conduit to an SQLite Database(add, change, delete, inquiry). Some of my potential clients have asked to see a sample of my work, but they don't have an Android device.
Other than just showing them screenshots etc., is there a way I could have them go to a website where they can actually run it & check it out.
I'm thinking there would be a programming element involved (convert app to a mobile website essentially?), hence posted this question here.
Not quite sure where to get started. Any help would be appreciated.
You can use one of the patterns like MVC/MVP/MVVM to create your core library and then develop additional UI variants for different clients: Android, java applet etc.
Alternatively you can develop a mobile web site as you suggested and use simple android app to navigate built-in browser to it. This might be somewhat transparent to most users. I think Android MSN client uses such an approach.
I see 2 relatively easy options.
Give them an .apk designed to only
run on the emulator (you can check
the ID, the emulator ID is 00000...)
and they can boot up an emulator and
run it. If you're worried about them
reverse engineering your .apk you
probably shouldn't go down this
route. Or if you don't want them to
have to install the emulator
Set up a virtual machine and let
your clients remote desktop into it.
Give them permissions to only run
the emulator or however you want to
set it up