http://iscoresports.com/

Instead of having to touch the "in Play" button and then choosing one of the many buttons to determine what happened it would be very cool if you could just drag the batter along the base path to the base he stopped at. In other words if the batter hit a double then you would just drag the batter to first and then to second in one motion. This would move the batter to second and score it a double. This would only be used for normal single, double, triple, or home runs.

We have had this suggestion before, but there are many things that are not accounted for. What if it is a single + error? What if there is a runner on first and you drag the batter to second? We are always looking for ways to improve, but we have to balance them against things that can go wrong. Thank you for the suggestion.

There are lots of little things like that that i think could help make the app easier to use in many ways. My biggest hurdle to using the software is the amount of "taps" and dialog reading that need to be done. Something as simple as a stolen base with multiple runners on sometimes takes several tries to enter because I have to tap on the runner, tap on the base they are going to then tap on steal. In bright light, I don't know how many times I've hit the wrong button and needed to start over.

Expanding on atiannicelli idea - I think it would be nice to consistently have 2 input options: basic - where the software makes a standardized set of ASSUMPTIONS for you. By default basic things like dragging a batter to second would be a double, dragging a baserunner to the next base for an assumed steal, buttons near the pitch location chart to indicate wild pitch / past ball when runners are on base (to make the dragging options even smoother), assuming a swinging third strike is in fact a strikeout, etc. All those little things really added up during the season - I found myself asking players "what happened" and entering things after the fact *MUCH* more than when I scored by hand.

The existing "step-by-step" mode would be for the exceptions and complex plays - basically it would be nice to have the best of both worlds!

webshowpro wrote: ...
All those little things really added up during the season - I found myself asking players "what happened" and entering things after the fact *MUCH* more than when I scored by hand.

The existing "step-by-step" mode would be for the exceptions and complex plays - basically it would be nice to have the best of both worlds!

The best of both worlds would be great but that is hard to program and even harder to support.. I too like the idea of a basic version and an advance version, but thought I would give some context on why I do not see that happening soon..

"back in the day" version 1.0 the community discussed pros and cons of a lite version, (similar to your basic), vs a pro version. At the same time weighing wish list for other device, beyond iphone, more features in app, use/integration with the web add ons, and other sports , basketball, football etc. Plus more ease of use ....

In my opinion.. it became obvious quickly, fix any bugs, add high desired features and Multiple platforms and multiple sports with web additions was much more desired by the user community at that time, than lite and pro versions. Plus Where to draw the line on a lite version feature vs pro was a no win.. different user levels, in both scorer and play. And the interdependencies in baseball and desire to be accurate vs easy were big challenges

Additionally FTM was concerned they would be viewed as greedy, marketing too many versions of what could be one app. although i assume they like sales, they have tried not to make multiple apps.. pro baseball, college, high school, little league, slow pitch fast pitch pitcher version, batter version etc etc. etc . Instead have opted to support the users with feature additions multiple platforms and add value to each release in a more of a one size fits all model.. With a strong eye to making user input easier where they can

Right or wrong that is some of the context I observed as an outsider as they weigh the pro and con of a basic version..


On a second front, I too find I take more time entering in iscore than I did on paper.. But less time overall. Plus my accuracy and completeness is much higher in iscore than it was on a paper version and in total less time and better product in the end, with much easier distribution and archives.


Thanks again for continued participation in the forum...

FTMSupport: To answer your questions: What if it is a single + error? I would only use the drag batter option for basic normal plays so I would use the "In Play" button to score that one.
What if there is a runner on first and you drag the batter to second? Then the program would treat it exactly like when you click on "in play" and then press the "double" button. In other words a new window would come up saying "What happened to the player on first?" Then you would answer it the normal way.

I've also seen other programs allow you to move a player by dragging and then press the baseline to edit what happened. If you don't press the baseline to edit the advancement then it goes in as a normal single or double, etc. But if you advance the runner to second and then press on the baseline from first to second you can indicate that there was an error that advanced the runner to second.

Don't get me wrong - I love the app - I guess, as webshowpro said, in most cases the basic play is all we need so it would be nice to be able to quickly move the batter/runner and assume the basic play happened. If something more interesting happened then the scorer goes to the "in Play" button and do it the current way.

While I;d really like 2 versions - one for spectators the other for scorekeepers - I'm not really asking for separate versions here - just expanding on the already existing shortcuts. The software already supports the complex entry needed for nearly every scenerio, and has a lot of shortcuts already.

I'd like the shortcuts to be the "primary" input method, and for them to make more assumptions to save taps. The (assumptions they make would be intelligent based on the current game situation -AND- user configurable settings.

The current dialogs we use for most tasks today would also be available via "advanced mode". That way we only have to go through the complex "wizards" when they are needed.

"FTMSupport: To answer your questions: What if it is a single + error? I would only use the drag batter option for basic normal plays so I would use the "In Play" button to score that one."

*You* would, but dozens of others wouldn't, and then they'd be up here complaining that they can't make that a single + error.

was thinking about this and thought .. how about a swipe of in play button for some quick plays (like we do quick outs)..

eg, basic single all runners advance 1. then prompt for location (besides being wordy for a button, I realized i would still want to know, location, where ball hit, and what type of hit, grounder, fly line , soft medium hard. so still have a number of buttons..

this got me thinking, i think the extra taps most people get hung up on are for the base runners, what happen to runner at x base? perhaps an Advance all runners one base button on the what happen to runner x screen would help simplify. / reduce taps?

just spitballing different ideas

+1 for above suggestion

The issue with trying to make any assumptions with the runners is that people will not pay close attention and actually leave runners on bases they should not be on. And as you know, you can not edit a base a runner made it to as a post game edit.

The assumption that a "basic single all runners advance 1" is probably not true. Usually on a single, a runner from second will try and score (thus "runners in scoring positions"), but not always. Any assumption we make would then require an "are you sure step" which would negate the savings in taps. If we added a "single with RISP scoring" and a "single with runners advancing one base" and a "single but runner on third does not advance" and a "single but runner on first goes to third", etc then you would actually spend more time looking for the right "shortcut" than if you had just known the consistent way of entering every play.

On a single, we do actually advance the runners one base by default, and you have to press "held up" on each base to confirm the runner stayed. The one idea we have heard that could be a time saver and not cause confusion / issues when multiple runners are on base is an "All Held" or "Hold All" or something like that to avoid pressing Held Up several times in a row.