Sticking with iPad

[elcray]

I scored all of last season on an iPad. The only issue I had, which I'm not blaming Apple on this one, was a single instance when the device overheated and shut down in the middle of the state tournament (105 degrees and no shade...it happens).

While I'm not as rabidly against Apple as I used to be, I certainly am invested heavily in the Android camp. All of my phones are android devices and all of our media and apps are android. So with that said, in the off season I have been experimenting with iScore on the Nexus 7. It is a great little device, but I just can't make myself make the move. The nexus 7 is the perfect size and battery life is great, but it has one fatal flaw (at least mine does): crashes that lead to reboots. While I have never had a reboot in the middle of iScore, it has happened enough times that I can't trust it in the environment of regular season.

Some of this decision is centered around the difficulty of using multiple devices in iScore. The difficulty in synchronizing information between an android device and an iPad makes it hard to commit to one direction and use the other as an emergency backup. So for now, I must continue to use the devil....I mean, the iPad.

[OhioTex]

I am a big fan or iScore for iPad. so not trying to change your opinion. but iScore for Android is debatably its equal.
The developers try hard to keep the platforms in relative synch with data and features.

I have not seen or heard of any platform issues transferring data between iPhone - IPad - Andorid . OPTIONS > DATA SHARE> is device neutral

As to overheating, consider yourself lucky, in direct sunlight i and others have experienced shutdowns at 80o in direct sun, the direct sun is the key - the screen tends to act as heat collectors. not sure will be different on andorid as the big panel just soaks up the sun.

[elcray]

With all due respect (and I mean that sincerely): using data sharing is a great option to share a single game with another coach, it is not in my opinion a viable solution to setting up a backup device. Having to import all games, all teams, all players, and then dealing with the respective mapping...it's just not a usable solution for me.

For me, an emergency backup needs to work like this: At any time, from any of my devices (android or iOS) I can enter my account code/password, and synchronize the data. That means that it pulls down all of the information from the web account to this device. When I get done scoring, I export as usual to ensure that all of the data is always on the web. If, in the middle of a game, my device runs low on battery, I exit out of the game, do an export, and then perform what I mentioned above on my backup. At that point I resume scoring on the backup. This could be handled between innings without missing data.

I guess what I am saying is that I want to know at any time that I can score with any device I can get my hands on, without first having to perform some crazy mapping step. I can even foresee a disaster preventing me from attending a game (I'm an IT guy who is on call 24/7). I call a parent with an iPhone or Android. They download the app from their marketplace, I give them the account and password and they sync their device and score the game.

[FTMSupport]

Mapping is not required most if the time. Data sharing allows you to transfer an in progress game. We also have the backup / restore you are requesting. Maybe you have not seen this:

http://iscoresports.com/baseball/kb/faq ... lldata.php

[OhioTex]

You are on call 24x7 for technology , so i am sure you appreciate the challanges.
And the economics involvrd for a ten dollar app.

[elcray]

Mapping is not required most if the time. Data sharing allows you to transfer an in progress game. We also have the backup / restore you are requesting. Maybe you have not seen this:

http://iscoresports.com/baseball/kb/faq ... lldata.php

Yea. I discovered that yesterday. I tried it on my Galaxy S3 and seemed to do what I am looking for. I will certainly give it a try during preseason.

Talk me through what happens when I perform this process on another device. I then score a game and do an export. Then should I send a restore to the primary device or just do an import from it?

[FTMSupport]

This process transfers the entire database from one device to another. So if you scored from a secondary device, you would want to export from that device, then do this transfer if you want the second device data to completely replace your primary device data.

In general, Data Sharing would be what we recommend as you can transfer a single game at a time (and you can even transfer an iScorecast to another device with the data share in which case the export is not required... like if you run out of battery while scoring a game), but it seems you do not like the data share process for some reason.

[OhioTex]

Data share is the expected way for shareing games between devices ...

The ability to whole scale swap out a database from one device to another, replacing (, not mergeing) onto a secondary device .. Has generally been used when changing devices permenantly (lost device or changed, phones, , or upgraded to new device)..and done by email to iscoreSupport...

That said it has been discussed on this board elsewhere the possibility of letting users (at their own risk) have the ability to do that via team admin web site. ( ie tell server to replace data on device a with b, then import.) that work flow would be on receiving device option> export .. .. admin web site (copy source device database and replace on device b. ) . .. Then on device b Option > import (recipient device) ,.. As i understand it, This is a potential future self serve capability.

Again, the expected method to share between devices at the user game level is data share

[FTMSupport]

OhioTex - apparently you missed that we added that already a while back. The link is in the thread above. Here it is again:

http://iscoresports.com/baseball/kb/faq ... lldata.php