4 ms·

We're currently making a HTML5 web app that works in Chrome and iOS Safari. It's an audio app (SpeakerBlast) where you sync the same audio across devices; used

We're currently making a HTML5 web app that works in Chrome and iOS Safari. It's an audio app (SpeakerBlast) where you sync the same audio across devices; used to amplify audio amongst friends or throughout your IP devices for gatherings, flash mobs & playing audio throughout your home! We feel it's easier for to tell your friends to go to this link to join in then, "Hey download this app so we can all play audio in sync." No doubt that the current market says native apps, but this will change within two to three years. Web technologies are catching up in regards to what can be achieved via Android (specifically Chrome) and Apple mobile web browsers.

peterhunt 13y ago
Absolutely. URLs are the #1 feature of the web that native apps are lacking. The second being metadata and search engine indexability of the content.
- mmahemoff 13y ago
  It's not entirely true that native apps can't deal with URLs. On Android, they can handle them well with intents and on iOS, they can at least open URLs of a certain protocol. The main issue is that the receiving user probably doesn't have the actually app. That's the benefit of web presence from a sharing/virality perspective.
mmahemoff 13y ago
Yes, you can do some pretty cool cross-browser stuff even today. "Web technologies are catching up in regards to what can be achieved via Android (specifically Chrome) and Apple mobile web browsers." This is assuming native platforms stand still, and they aren't; the web's caught in their cross-fire. Whenever you think something is "done", it's rarely the case. (I know you didn't say that, but it's a related argument people sometimes use in favour of the web.) iOS and Android in a few years could be dealing with home automation, cars, wearables, etc., and while some developers today might say "oh but we just do mobile", in the future that might be like saying "oh we just do 7" tablets". The "catching up argument also assumes web standards are converging, and in the past two years, the increased pace of innovation has made some web technologies diverge. Such as the offline technologies I mentioned in the linked article.

peterhunt 13y ago

Absolutely. URLs are the #1 feature of the web that native apps are lacking. The second being metadata and search engine indexability of the content.

mmahemoff 13y ago
It's not entirely true that native apps can't deal with URLs. On Android, they can handle them well with intents and on iOS, they can at least open URLs of a certain protocol. The main issue is that the receiving user probably doesn't have the actually app. That's the benefit of web presence from a sharing/virality perspective.

mmahemoff 13y ago

Yes, you can do some pretty cool cross-browser stuff even today. "Web technologies are catching up in regards to what can be achieved via Android (specifically Chrome) and Apple mobile web browsers." This is assuming native platforms stand still, and they aren't; the web's caught in their cross-fire. Whenever you think something is "done", it's rarely the case. (I know you didn't say that, but it's a related argument people sometimes use in favour of the web.) iOS and Android in a few years could be dealing with home automation, cars, wearables, etc., and while some developers today might say "oh but we just do mobile", in the future that might be like saying "oh we just do 7" tablets". The "catching up argument also assumes web standards are converging, and in the past two years, the increased pace of innovation has made some web technologies diverge. Such as the offline technologies I mentioned in the linked article.