Install APK in Wearable device without Android Studio,Eclipse or ADB

This is the big concern about wearable development how I will install wearable apk in wearable device? We can install it three ways :
 - Using android development IDE (Android Studio, Eclipse etc)
 - Using ADB without IDE
 - Direct from play store
But main problem is client are not always well trained to install apk using IDE or ADB. So what is the easiest way?

Easiest way to install wearable apk :

1. Make sure your package name of wearable and mobile are same.Go to AndroidManifest .xml file both these module and check whether these are same or not. If same then ok otherwise you have make them same.
2. Normally, There two apk's are available in wearable project one is "Mobile APK" and another is "Wearable APK".
3. We have to build signed apk for "Mobile apk". If any one doesn't know how to build signed apk you ca see this video - click here.
4. When APK build successfully you can find it in "Your_Project\mobile" folder.
5. Then send it to your phone which is connected to wearable device.
6. Then install it on your mobile.
7. When the handheld app will connect with the wear, it will install/update the wear-apk on the wearable device.
8. The mobile app can be empty, without Activities, but you have to declare the same package in AndroidManifest for both.

Conclusion :

You can send signed apk using email or any other way to your client to install wearable apk to their device following these steps.
Location: Dhaka, Bangladesh

Comments

Post a Comment

Popular posts from this blog

Marquee Text Android: Using RecyclerView like Ticker

Image
Why this article? Sometimes in our Android, apps need a marquee text effect, like a smooth auto scroll horizontally or vertically. Example For breaking news apps, there is a necessary functionality, which shows the breaking news, such as on a horizontal scroll. In share market apps, the top app should give an auto scroll effect to show the text. In Android, there is no perfect library for marquee text but in this blog, I will give the simplest solution for marquee text. Procedure Add RecyclerView, as per your desire and also add dependency. XML 1. <android.support.v7.widget.RecyclerView   2.     android:id="@+id/rec_all_stocks"   3.     android:layout_width="match_parent"   4.     android:layout_height="match_parent"   5.     android:scrollbars="vertical"   6.     android:layout_alignParentLeft="true"   7.     android:layout_alignParentStart="true"></android.support.v7.widget.RecyclerView>  
Read more

Android Spinner with Dialog Box

Why this post? Sometimes for visual effect, we need to show the spinner item in a dialog box which is most customizable and designable. UX engineers also try to make the more complex situation. That's why I made a spinner where spinners item will be shown in the dialogue box. Techniques which I used: For this purpose, I used Dialog, RecyclerView and EditText. 1. When clicked on EditText a Dialog Box will appear. 2. Dialog box holds a RecyclerView with an adapter where adapter holds a TextView. 3. Then implement a OnItemClick listener in RecyclerView. 4. Then item text will set on EditText. Codes with Description: Dialog layout: dialog.xml <? xml version= "1.0" encoding= "utf-8" ?> < LinearLayout xmlns: android = "http://schemas.android.com/apk/res/android" android :orientation= "vertical" android :layout_width= "match_parent" android :layout_height= "match_parent" > <
Read more

Comparison Between SOAP and REST

SOAP and REST can't be compared directly since the first is a protocol (or at least tries to be) and the second is an architectural style. This is probably one of the sources of confusion around it since people tend to call REST any HTTP API that isn't SOAP. Pushing things a little and trying to establish a comparison, the main difference between SOAP and REST is the degree of coupling between client and server implementations. A SOAP client works like a custom desktop application, tightly coupled to the server. There's a rigid contract between client and server, and everything is expected to break if either side changes anything. You need constant updates following any change, but it's easier to ascertain if the contract is being followed. A REST client is more like a browser. It's a generic client that knows how to use a protocol and standardized methods, and an application has to fit inside that. You don't violate the protocol standards by creating extr
Read more