You can now remotely install an app in a simple way. No need for Windows 10 SDK to get winappdeploycmd, You can use Device Manager in a browser locally or on the phone to do it. Here's how. This blog covers the basics about app packages, deployment and setting up for sideloading. The next blog covers remote app installation and in phone app installation using Device Manager running in a browser.
if you set your Windows 10 (Mobile) Phone in Developer Mode (perhaps Sideloading is all you need) then you can fire up a web browser where the Appx file is located and remotely install the app on your phone. Alternatively you can actually file up the (Edge) browser on your phone after copying the package to it and install the app package there!
You develop a Universal Windows Platform (UWP, previously called a Store App) in Visual Studio (2015 Release 2). You typically deploy to a phone over a USB cable during development. The phone has to be in developer mode. Once developed, you publish the app in The Store where any user can get the app. It is though thoroughly tested and repackaged before being published by Microsoft. Alternatively if you want some users to try your app you can pass them the package and they can install it if the phone is in Sideload (or Developer) Mode.
They would need to have the standalone version of Windows 10 SDK installed on a Windows 10 system to do the sideloading or have Visual Studio 2015 (Release 2) installed, which includes the SDK. Using USB connectivity between the phone and PC, you run the Visual Studio Developer Command prompt and change directory to the package folder and run a command such as:
winappdeploycmd" install -file .\myapp_220.127.116.11_ARM.appx -ip 127.0.0.1
Once the app development and debugging is complete you create the package. To do this you right click on the app project and select Store-Create App Packages
Note: If you have dependency projects in the solution you only do Packaging (once) via the main app project.
You can click on these images to expand them.
On the next dialog choose No (The package isn't intended for The Store):
On the next dialog choose Never (Generate App Bundle), ARM only and Release and No Symbol files:
The press [Create] and the package build starts.
When done you get a dialog that tells you where in the Solution the package is located. Ignore the Validation.
Open the folder for the apps package(s). Any subsequent package builds will be located under this folder.
Open the folder to note the package and certificate files generated. Ignore the PowerShell file. Note the folder path (Its needed later).
Note also the Dependencies folder. Open it and note the app's dependencies.
http://<phone's ipaddress> or http://<phonename>
http://localhost or http://127.0.0.1