IOS vs. Android. Which is easier to develop for, what wireless communication should vapes use?

[SirCrackKillaH]

I don't know much about the development of apps. Why would IOS be chosen as the standard over android? Most of the technology companies that I'm aware of that have apps for their products seem to go IOS first before eventually going Android. Why is this? I would assume both are pretty equal as far as the amount of time required to make them. Is it because of targeted demographic? Is it assumed that those with IOS have more disposable income? Why does it always seem like Apple apps are more refined?

As far as Apple devices are concerned, they are considered more snappy because the hardware and software are developed together. This in my mind leads to better overall reliability. Is this ill conceived? Now for vapes, what wireless tech utilizes the least amount of power overall? Figure even in standby, power is being used, so isn't Bluetooth wasteful? Is there an alternative?

 

[Silver420Surfer]

Why in hell do our vaporizers need wireless or bluetooth? There isn't a single reason in the world that would make sense to this longtime, medical user. Gimmick and nothing else.

My negativiy wasn't directed at you @SirCrackKillaH, just the stupidity of companies doing this.

 

[Dramma Lamma]

I agree that the phone and app has no real point in even existing in vapes.
Cheesy gimmick.

Most of the technology companies that I'm aware of that have apps for their products seem to go IOS first before eventually going Android. Why is this?

A potential answer there is that IOS has less available supported versions at any given moment and less variation in hardware. So from a programming perspective its easier to work with and optimize if there is less hardware / firmware variation. This is why PC video games have more bugs than console games in general as the consoles are all working with effectively the same hardware.

Apple apps are more polished because apple basically sifts through the programming and takes longer to approve the app to get published to the app store, which forces the developer to look closely and get it right the first time. It also ties back into the less variation in firmware / hardware thing.

Is there an alternative?

Alternatives, as in what? if your thing has to have a remote but you want to save batteryor avoid apps then the option is good old IR or 2.4ghz control.

Or you can just design a quality product that works well on it's own and doesn't expect me to also mess with some stupid app. A prime example of that would be mighty vs crafty.