Enhancement requests after 1.60

[FTMSupport]

There are many styles of scoring by hand, and using iScore actually allows us to show a scorecard in even more detail than you would typically be able to track by hand. There is not a single rigth or wrong way.

That being said, here is a pretty good reference site:

http://swingleydev.com/baseball/first.php

We do most of what this site shows, and have added some of our own conventions as well, but it is a pretty good step by step reference with several pages of examples.

[navarre]

First, let me say that you already have a great program. I've used scoring software for Palm and Pocket PC for several years, but your program is much more intuitive.

I've kept up with the enhancement requests, and you are doing a great job of responding to them. I agree with the priorities you have mentioned in your replies - you are on the right track. I have a couple of user interface suggestions that hopefully won't be too difficult to include as you are making your upgrades. I have attached screen shots of my suggestions discussed below.

The first concerns the 'batter safe' selection page. In the latest release, you added some new events and had to add a second page ('More...') to include all the options. I don't have any complaint about that layout, but the first page is quite full with buttons and has very little space between them. I occasionally tap the wrong event due to the tight layout. Since you have a second page now, could you remove the last row from the first page and spread the buttons out vertically to give us a little margin for error? It looks like you could add about 6px of vertical space between each row if you removed one row.

To minimize the changes to the first page, I suggest that you move the 'Catcher Obstruction' button to the second page (it is rarely used anyway), and then move the 'More' button down beside the 'Cancel' button as the bottom row of the page. This really makes more sense from a user interface standpoint since 'More' is not an event, but is really a navigation button like the Cancel button. In my example screen shot I also changed the background color behind the navigation row to separate it visually from all the event buttons. For consistency, you should then use the wider spacing between rows for the second 'batter safe' page, and for the 'batter out' page as well (and maybe use the same background behind the Cancel button on that page as on the safe pages). See the attached screen shots for examples.

The other layout suggestion I have is on the 'runner/batter advance' pages. The text at the top: 'What happened to...' and the player's number and name are all one string of text, and the players' names get split and wrap to the second line. It would be easier to read if the question was on the first line, and the player number and name were on the second line (and maybe in a bold font to make it stand out). See the attached screen shot for an example.

Sorry for the long-winded explanations. Thanks for listening, and keep up the great work. This program will get a lot of use at our high school starting in a couple of weeks for the summer ball season.

Thanks again.

[FTMSupport]

Thank you for the suggestions... we will take these ideas into consideration as we continue trying to enhance the usability even further.

[superoptimus]

I was wondering how high of a priority getting 1-1 pitch counts for batters is. I was excited to see the enhancements and the pitcher pitch count, but was bummed to not be able to put the 1-1 on there. It effects the pitchers stats harshly.

LOVE THE UPDATE!! THIS IS THE MOST INTERACTIVE APP I HAVE.

superoptimus

[Phantom Sage]

There are many styles of scoring by hand, and using iScore actually allows us to show a scorecard in even more detail than you would typically be able to track by hand. There is not a single rigth or wrong way.

That being said, here is a pretty good reference site:

http://swingleydev.com/baseball/first.php

We do most of what this site shows, and have added some of our own conventions as well, but it is a pretty good step by step reference with several pages of examples.

For those rare times when you simply run out of battery life and have another game to score - or innings to finish, I prefer a little known method of scorekeeping I believe is called "situational" scoring by a person I found while googling for newer methods of keeping score that includes many of the things you want to know but are not accomodate in a traditional scorebook. (creator is Alex Reisner)

iScore grabs a lot more information on a traditional sheet than you could actually track as accurately on paper. But for those times that you simply can't get all of the info loaded prior to start or do not have enough battery life, I use this method and then transfer data to iScore fairly rapidly.

[FTMSupport]

Thanks for the tip.

[Hooperjd]

I would like to have an advancing a base runner option of "throw". For example, batter hits a single and advances to second on the throw home to get another runner out.

Thanks

[FTMSupport]

You will be happy to hear we have "Advance on Throw" ready for our next release (v1.70). Thank you.

[jaybird1452]

I must say I love the play by play option that was added on the latest version. Last night we had a double header and the tough part is getting lineups entered quickly before the game starts. Would it be possible to have the scorecard default to the last games lineup?? This would have helped a lot last night. I think it would benefit many people because a majority of lineups are very similar to the last games lineup. If minor changes are done in the upcoming game then it will be quick to make the change.

[bsweetser]

If you set up the lineup in the Team Manager, this is the default lineup that is used when you start a new game. Then you only need to make adjustments for the game.

ben