Lets assume that the intranet has SSL and the users are using Chrome in Android, will progressive web apps work? Will it have offline caching?
Lets assume also that the push notification service will be sitting in their network, will it also have notifications?
A Progressive Web app works where any website works, as long as it has a service worker, a manifest and SSL. When people are outside the company, they'd see the offline version.
Push notifications might work as well, but you need to be inside the company network to receive them.
Related
So Suppose we have a pwa app say X. When we install that app on homescreen, do we get two service workers one on browser say chrome and one in the native app? How push notifications will work in such cases, do we have to get subscription for native app separately for sending push notification to service worker of native app. And will these notifications appear in app or on chrome browser?
P.S By native app I mean pwa app installed on homescreen
Add to home screen does not add a native app to your device or desktop. It's still using browser resources. There's one service worker and one push notifications flow.
I've created a real photobooth which is a camera in a housing with an raspberry pi running a webserver and handling all the photo stuff. The frontend for this is an tablet with a browser pointing at the webserver running on the pi (on local network).
The functions are pretty simple: Take a picture (or a strip of four), view the gallery, download and mail the photos. Now I'd like to integrate a photo upload to Facebook.
Is this possible with an application that is not hosted public? The booth has internet access via 3G or available Wifi. But the pi's webserver is only available locally.
My first Idea was to have the postback send to a script running on my website that redirects me hardocded to the local adress. This is working, but is this allowed?
For publish permissions I need to submit the app for review. But how can Facebook review my app? It's not available public.
Thank you in advance.
Arne
I am using a proxy for logging purposes and blocking malicious sites.
I recently installed a squid3 proxy setup with SquidGuard. I have my iOS devices connected to it and all it working well except for 2 apps. The iOS Facebook and Twitter app will not update content, and eventually times out. I actually want the content to update. This only happens when coming out through the proxy. If I turn wifi off and connect 4G it works. All other internet apps on the iOS device work except Twitter and Facebook. Any thoughts? I am using a very simple proxy squid.conf file and SquidGuard is blocking a bunch of spyware/ad domains, but not facebook.com or twitter.com or akami.com/akamihd.com. Thanks!
By the looks of it, the Facebook app for iOS does not support proxies at all. On my iPad, for instance, the app tries to connect directly to Facebook irrespective of proxy settings. One workaround is to redirect all of your device's traffic through a device that performs intercepting proxying
We plan to manufacture a device that we want it to communicate with Facebook. If the user presses a button on the device, we want something to appear on users wall as a post. It means that the device will post on behalf of the user on Facebook.
As we see from the Facebook developer page, the types of applications are a Facebook app, a web app or a mobile app. The thing we have just explained does not belong to any of these categories. For instance, it is not a web app because the device does only support http connection but does not have a built-in web browser. It is not an Andorid or iOs app because the operating system in this device is none of these.
What would you suggest for this kind of application?
Thanks in advance.
Definitely look into http://developers.facebook.com/docs/authentication/devices/
Your other decent option would be to run an HTTP server on your device that users could connect to from a computer or phone to authenticate.
Once authorized, a simple HTTP request is all that it will take to share anything.
Edit: Just noticed that Facebook is no longer accepting applications for new partners with the auth device pattern. This is definitely what you want. You could try contacting them anyways.
Possible Answer = make it web app but dont forget the facebook policies about the user privacy issues. Your device can send a signal to your server and server can make the post i think it is possible (hmmm but to acquire access token again your clients have to login your webapp again every 60 days, there must be a better solution)
I am also working on similar problem
I have a prototype device for jogging wrist band and I am trying to post a wall story about number of steps in current day and the tempo on behalf of a user by just clicking on a button on the machine when it is connected to wlan or android phone in a wireless fashion.
We're planning an app which, among other things, is supposed to integrate a facebook chat.
We're discussing about the push notifications for receiving messages while the app's in background. What comes to mind is a proxy server for the chat, that'd actually connect to the facebook chat, and the iPhone app would connect to the proxy.
Then, it's easy to have the proxy server act as a push notification server.
Is this the only way to go, or are we making this more complex than it needs to be?
Any input is appreciated. Thanks.
To do push notification (App is closed, user receive a message and an alert appear on the iPhone), that's the only way, because every app need an unique certificate to send push notifications. This mean that official Facebook servers can't push for third-party applications. You need a proxy that keep a connection open to FB and push alerts to Apple's Push Notification Server when needed.
Inside the app, instead, you can connect directly by opening a socket to Facebook's servers and use a Jabber library for ObjC. This allows another approach: Local Notifications. They're similar to Push, but they doesn't need a proxy server: it's the application running on user's device that keep an open connection (even when the app is in background) with Chat Server.
This is the documentation that covers both type of notification: Local and Push Notification Programming Guide
Facebook's chat system is a Jabber server, so I think you are making it more complex than you need to.