I am in the planning stages of creating a social experiment. I am trying to see if it is feasible to develop an app for android to accompany participants using the parameters below. Nothing is set in stone. More could be added as options become available. If you care to know more, just ask. If you can help, that would be a plus.
Android app parameters:
Google Maps Api for proximity alerts to allow a participants to know when a clue is near and for an on-screen visual aid.
Ability to communicate with other app holders whether through text or speech
Integration with G+ - to publicly post what they have found
Ability to track other players real time (ability to disable public player tracking.)
Ability to create a profile to be shared via NFC
Minimize the need for a server to cache information
Minimize graphics
Utilize NFC to collect necessary information at physical locations.
The ability to edit data on a bracelet with an NFC chip embedded within.
The ability to track actions and locations(only when at game designated public locations)
Not sure if I want to embed information in the app or retrieve it on a server. (Information will change on a regular basis.)
Bump. I'm just looking for any kind of feedback on direction
Sent from my SM-N900T using XDA Premium 4 mobile app
MyInkedSpace is a tattoo social network and this first release of the native Windows Phone app provides a subset of the sites features, such as private messaging, browsing tattoo pictures, viewing profiles, finding members to contact, seeing who's viewed you, uploading pictures, etc. More features are planned for future updates to the app. MyInkedSpace has nearly 70k members, most of which have tattoos. The app requires Windows Phone 8.1.
I can't post the link since I'm still under the 10 post limit, but it can be found in the store on your Windows phone or at windowsphone.com by searching for MyInkedSpace.
Hey there,
I am currently developing some kind of entertainment cloud server for Android. It runs on any Android device and turns your phone into a personal cloud server, remote media player, webcam and much more.
You can manage access and permissions with the help of users and groups and employ it as your personal messenger, invite your friends and automatically sync data accross multiple devices.
The core is a robust, leightweight, SSL secured and Android optimized web server (MISS) that makes it possible to access the cloud from any browser. All unnecessary overhead is removed to deliver great performance, even on slow devices. The web interface is designed to be rendered really fast on phones and tablets.
Another central part will be the media plugin. An old android device can be a great remote controlled media player or web radio with a fancy display and cool visualizers.
I cannot disclose all the features, yet. It would be quite a list, anyway.
Another thing that I really love about this project is the fact that it might help reduce electronic waste and power consumption. One could call it regional syncing :cyclops:
I am really curious about your opinions. The development is in progress, and I hope the effort is not in vain.
I created some drafts to explain the basics: imgur.com/a/LXu24
Implementing a social login option in your Android or iOS app makes it possible for your users to sign in on every device and use their last saved settings and states. You can use a variety of methods to let the user sign in to the app, which one are you using and how many? I wrote a short article about it not too long ago.
In case of an app of mine with over 8,000 downloads, there are 3,600 Facebook signups, 4,500 email signups and 500 twitter signups (it's a social app so there's no option to use it without signing in). Users are not coming from any of our social sites because we don't really have a social presence, so the numbers are totally random. I there's no one-size-fits-all answer, but I thought we could help each other.
Would you share your experiences and ratio?
Not sure if I’m on-topic here or not, but here goes... I am responsible for the setup/configuration of WiFi routers in various restaurants and venues. We are simply using the built-in splash page functionality of the router to, upon connection, present a simple marketing message and daily special offer via an extremely simple, static external HTML page, rather than the login page that many venues present (airports, coffee shops, McDonalds, etc.).
After connecting to our SSID with a PC or mobile device, users are presented with a customized splash page where our venue’s latest “offer of the day” banner ad is presented, which links via a standard hyperlink out to a PDF coupon for them to redeem said offer. There are also a couple of other simple items on the page, such as a menu with links to other offers, and an embedded Google Map to the venue in question.
All seems to be OK on PCs and iPad/iPhone devices. However, we are running into a problem on Android devices – specifically, Android devices using newer/more recent versions of the Android OS.
The problem is that Google has made a change to newer versions of Android so that WiFi connection login/splash/confirmation pages no longer come up in the default Web browser of the phone/tablet in question. Instead, they seem to come up in some kind of built-in notification window simply titled “Sign-in to network” – it does not seem to be a full-blown, feature-compliant browser, but rather a panel of sorts built into Android. And when our basic, mainly static HTML page loads within this alert window, none of the standard HTML features (such as hyperlinks) seem to work. A window appears with the title “Sign-in to network”, and our splash page appears on within it, but the standard HTML hyperlink from our special offer graphic (to a PDF file) does not work. Clicking it has no effect. Our menu underneath that does not seem to open (it’s automatically collapsed on mobile devices), and none of the links within it work properly, and our embedded Google Map does not appear at all. It’s as if this alert window or whatever we call it does not support the basic features of HTML pages in any way.
There appears to be no way for me to programmatically force the Android client to “escape” from this proprietary panel and open up a page in their default browser. I’ve tried placing various forms of client and server side “push/redirect” code on the page in an effort to escape from this alert window and cue the default browser to open, with no luck. No matter what I do, it seems that they Android phones always load the splash page within a “sign-in to network” notification page rather than a browser, and that this notification panel is not fully functional for even basic HTML features such as <a> hyperlinks, javascript, or embedded items.
It’s possible that Android’s proprietary “sign-in to network” panel is apparently seeking some sort of acknowledgement of a successful "login" in order to proceed with any subsequent browsing. But if so, I don’t know what constitutes “acknowledgement”. Perhaps there some way to force a hidden form submission or link click programmatically to force the Android device to accept/acknowledge the connection just as if the user had logged in normally, so that we can then proceed to subsequent Web browsing?
Has anyone experienced this problem, or have any ideas as to whether there’s a work-around or coding-based solution to this difficulty?
Thanks very much for your help in advance.
UPDATE: I've been in touch with the Google developers of the sign-in panel... they indicated that "captive portal sign-in pages are displayed in an Android WebView, which uses much of the same code as the Chrome browser. The sign-in app is very simple, you can see all of its source code here.
One second after each navigation (including the initial page load), the app probes to see if the user has successfully signed into the network. This probe is done by fetching a URL that should give back a 204 response."
Based on this, I am making the assumption that until captive portal sign-in app probes to see if the user is successfully signed in, all other navigation and many other features on the page are disabled, and that the full functionality of the WebView panel is restored after a successful sign-in to the network. But if so how can I successfully "signal" to the sign-in app that the user is, in fact, signed in (or rather, that no sign is in necessary or desired)? Is there something programmatically that I can do in the page code to ensure this, so that the viewer can then proceed to normal Web navigation within the panel, and so forth?
Any insight into how this works from anyone here would be greatly appreciated!
Thanks!