So, I would like to have a Windows Phone app "connected" at ALL TIME with a Windows service.
That means that the service would need to know if a device has been turned off or lost network connection within seconds after it happens. On iOS and Android we keep this connection up with sockets. But this doesn't seems to be possible with background tasks on Windows Phone?
Is there somehow we could "ping" the server/service more often then every 30 mins from a scheduled task? The app will only be used by known people so if there is a possibility to "fake" a music app och location app that would do it. The app will probably be released as a enterprise company app so all users will be aware of the possible "battery drain" that could be caused.
If using Push notification, how long can it take before a device gets it and could the service know right away if that device received it?
You can use geolocation service and keep your app in background or even fake audio agent. You are free with choice because company apps have no public certification process.
Here is some info about Company Hub and enterprise deployment of Windows Phone 8 apps.
Related
I am in the digital signage business for small businesses. We have created an app that runs digital signage through the raspberry pi using Windows iot. Everything works great but what if one day we wanted to make changes to the app. Is there a way to update the app without having to manually do it on site. I would prefer having the app do it programmically through regular checks but I'm not finding anything. Wish there was a App Store mechanism for the pi to update apps. Any ideas on this?
All devices running Windows IoT Core run a small webserver instance on port 8080. You can reach this by visiting http://DEVICEIPADDRESS:8080
The default credentials are:
U:Administrator
P:p#ssw0rd
Within the portal, you can provision and deploy apps remotely using the App Manager by selecting "Apps" along the left-hand pane.
If you setup firewall rules to allow outbound traffic to the Windows IoT Core device you may be able to deploy updates remotely.
Currently there is no app store for windows iot but it is possible to create your own. You could implement this functionality using a push or pull system with Azure.
Push - azure pushes updates to the devices.
Pull - the device asks azure for updates
Get started with Event Hubs (tutorial describing how to implement Event Hubs in Azure)
Another option could be to write your own REST API on a server (Azure or your own server).
While working with Windows Phone Push Notifications, I got myself stuck in the part of creating the "cloud web service" to receive the negotiated URL and retrieve updates to the mobile device.Is it possible to create this Web Service without using Windows Azure services (I don't want to pay anything, I just want to push with my services to my apps)? And how can I create this Cloud Web Service.
I haven't worked extensively with Windows Phone 8.1. Check this webpage for Windows Phone 8 -
https://msdn.microsoft.com/en-us/library/windows/apps/hh202970%28v=vs.105%29.aspx
You will get a URL for each device you want to get notification on through the app you create. Taking help from the above link, you can create a local server (Cloud Web Service) for testing push notifications for your test devices.
I have developed Windows Phone Silverlight application (support 8.0 and 8.1) for my client request. The client is goint to publish the application in WP app store, but first he must check on his phone if everything is OK with the application.
The application was developed with Visual Studio 2013, I've got developer account and own phone assigned to this account on which I have tested the application.
The question is, how can my client install the application on his own phone skipping windows app store? I have sent him builded *.xap file but he had a some problems with installation (Cannot install company application)?
You can submit your app to Windows Phone Store BETA. Your app will by certified quickly, and your client will be able to download it just like any other app from Store. The difference is that it will be visible and possible only for him.
Log in to you DevCenter account, click Submit App. Then, in App info section expand More options and select Beta. Then you can provide your client's mail.
I'm not sure, but I think that the name of the app should not be the same as the final version. So you can name it "My App Beta" to avoid future name conflict with the final version.
One more thing. When your app pass certification process, you have to send the link to the app to your client, because he won't get any notification.
I noticed an app in Windows Phone Store, it can restart WP device, How does the app do it?
http://www.windowsphone.com/en-us/store/app/%E4%B8%80%E9%94%AE%E9%87%8D%E5%90%AF/75ed45c3-8268-4ca7-b405-17a31ded3810
There is no way to do it using public API in the SDK. Maybe there is some "not so public" API ... or the app just crashes so horribly that the phone restarts.
Anyway, you should not want to do this and such app should never have passed certification.
I have Windows Phone 8 emulator running and a sample app is registering and I receive the URI but when I try to send a notification, I'm not receiving in the emulator. I used to be able to use the sample app with WP7 emulator and it was working and I'm able to access internet on the WP8 but not the notification. Any pointers to fix this will be great!
This is what I saw happening:
1- If I didn't open the app after receiving multiple notification it looks like the OS will not show notification anymore.
2- if you try to send too many notifications.
3- If the app is open the notification will not show as a toast.
4- Sometime I had to open the browser and go to website to force the device to connect to the internet, probably because the phone was on wifi.
It's a pretty open question, since there might be multiple problems, but start with this (source: MSDN):
The push client service on Windows Phone Emulator must be ready before
you can use push notification APIs. Push client service on the
emulator takes two minutes to activate after you start the emulator,
starting from when the Start screen first appears.