K
K
KhanTengri2011-06-02 06:09:08
Android
KhanTengri, 2011-06-02 06:09:08

Web-applications: Question for Android and iOS gadget owners

I want to make something like an ICQ client, but browser-based.
In addition to desktops, this application should also work on devices running Android and iOS.

Well, that is, in the case of gadgets, it will not be a traditional application from the Android Market or the Apple App Store, but the same page on the Internet, opening which you can send and receive messages. This page, like the original ICQ client, must be open on the device all the time (at the request of the user, of course). And when a new message arrives, the owner of the device must be notified about it.
Because at the moment I am not the owner of a gadget for Android or iOS, the question arose:

Is it possible for the owner of these devices to constantly keep a certain page open in the browser, while so that it does not interfere with him to perform other tasks and there is an opportunity to beacon him about a message that has just arrived?

And a sub-question: what would it look like?

ZYZH Excuse me, tongue-tied in the morning, but I need to get an answer to this question today.

UPD: http://usr.org/test/audio.html

UPD2: Whoever has the opportunity, you can check on Android

http://www.jplayer.org/HTML5.Audio.Support/

Are there green items and, most importantly, will the music play for the greens (if any) if the page is in the background

Answer the question

In order to leave comments, you need to log in

7 answer(s)
N
Nicholas, 2011-06-02
@pnick

About iPhone/iPad: You can open a page in Safari and switch to another app. Safari will be remembered. I don’t know about meowing - I have never seen an alert from a web page.
IMHO, you can make it more interesting: under the iPhone there was a client for VKontakte - it was just a browser for a specific site. It is done very simply, it is easy to screw the necessary "meows". Yes, and it is easier to distribute this business in the appstore than the web-app.
Dare!

R
Roman, 2011-06-02
@WNeZRoS

Android: You can open pages and leave them in memory, but none of their content will run in the background (scripts, flash, etc).

M
Maxim Ponomarev, 2011-06-02
@maxvipon

The web page may be in the background.
A notification for a web page can be received when not on the web page, but will only be visible when you open it from the background. Those. the browser will not be able to notify the user that a web page has been updated. This is an application privilege.
For now, this is true for both platforms.

C
ChemAli, 2011-06-02
@ChemAli

LG Optimus One/ Android 2.2.1 doesn't meow your page at all.

D
Dmitry Guketlev, 2011-06-02
@Yavanosta

Desire S
Android 2.3
built-in browser - no sound
Opera mobile - no sound.
You were right about unloading pages from the background. Think about the target audience of your development. I wouldn't use this.

E
Enuriru, 2011-06-02
@Enuriru

iPhone 3G - no sound.

M
MegaDiablo, 2013-11-15
@MegaDiablo

For Android, the following will be true:

1) We cannot guarantee under which web browser your page will open. Some of the most popular are Default(standard), Opera(there are already 3 of them 12/15/mini(yes, they still manage to use it)), Dolphin. These are the most popular.

2) Each Browser may behave differently on your actions. For example, when minimized, it will stop the execution of all scripts and go to sleep to save the processor. Therefore, we cannot guarantee any behavior on the phone.

3) Almost all browsers will behave actively while the page is open, but as soon as you switch to another tab, and even more so if you minimize the application, the page will become inactive and nothing will come from it.

4) As already correctly noted, we cannot guarantee that the browser application will not be unloaded from memory after it is minimized. These are Android features.

PS

He advised me to reconsider the value of this application, since there are already enough native applications of this nature for Android.

If you intend to make this application, then I would advise you to write a small application with a WebView inside and already independently control the process of the application. With this approach, you will be able to access the Android API and at the same time retain the interface and functionality that is written in the WEB.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question