iFly GPS Forum

We have a new Forum!  Go here to get started: https://adventurepilot.community.forum.  
The new forum is easier to use and much more capable than the old, we hope you will join our community! 

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.
HomeHomeDiscussionsDiscussionsiFly Wish-ListiFly Wish-List"Featureitis" but still a suggestion."Featureitis" but still a suggestion.
Previous
 
Next
New Post
6/26/2015 12:03 PM
 

I spent a number of years beta testing for one of the major Windows EFB vendors. One thing I learned is that adding features has downsides. First, it make the UI more complicated, often driving buttons to be smaller and/or more crowded. Second, the additions to the UI are rarely where you would make them if you were starting with a clean sheet of paper for UI design. Instead they end up scabbed on to menus or screens where they really don't fit very well, making the UI even more difficulat to learn and use. Vendors are loathe to rip-up and re-do a UI to clean it up, fearing the wrath and possible loss from the installed base.

Unfortunately, the features race in tablet EFBs guarantees rampant featureitis and consequent UI deterioration. So I have not chimed in here much with feature requests.

But I do have a suggestion.

With charts on EFBs we have the alternative of looking at a tiny chart area and being able to read the legends or we can zoom back and see more of the chart but are able to read nothing. One place this can become an issue is when the nice man says "Bugsmasher N12345 I have a reroute for your, advise ready to copy," then he gives you an intersection that you never heard of.

So, how about a long hold on the zoom + or - buttons to bring up a "zoom to waypoint" option? The user could then select the type of waypoint and type it in. All of the search logic already exists for flight planning anyway. The user then hits "Go" and the map display comes up with the selected waypoint centered and at a magnification that allows reading the map text.

From that point, nothing needs to change. The user can add the point to his flight plan, zoom back as necessary to see his little airplane and his course line, etc. Everything he might want to do is already in the UI.

The new code to do this would seem to be minimal. (But of course all things are easy to someone who does not have to do them.) The only UI damage would be loss of the automatic repeat on the zoom buttons, and the feature would not intrude anywhere else in the UI.

 
New Post
6/26/2015 12:45 PM
 
Tinker - That is probable a great suggestion for IFR flying. However, for those of us who don't want to talk to the 'nice man', i.e. - VFR only, this would only add to UI complexity. In order to make everyone happy, perhaps it is time for AP to consider developing two apps - one for VFR and the other for IFR. - Walter? Shane? - Jim Williams
 
New Post
6/26/2015 12:57 PM
 

We've actually had some internal conversation to look at either splitting the app or having a Simple and Advanced mode, but that was shelved for the time being. As for the Touch and Hold on the Zoom +/-. that is already taken, holding the Zoom +/- will enter rapid zoom. There may be somewhere else to make this happen. Sounds like an interesting suggestion to consider. Thanks for the feedback and suggestion. Added to the Wish-List.


Shane Woodson
Vice President | Adventure Pilot LLC.
 
New Post
6/26/2015 1:10 PM
 

I smiled at your comments on featureitis.

Steve Gibson, hard drive guru of SpinRite fame and now long time host of SecurityNow! (with Leo Laporte), once echoed the observation of some other computer guru that it really takes 3 iterations of a product before it's "right." On the first iteration, you're just getting stuff done. In the second, you're fixing all the bugs and adding things you should have added at first. On the third, you do a clean sheet build, incorporating all the things you learned in iterations 1 and 2. (This explains why it took my airplane partner and I ten years to build our Glasair. We did everything three times.)

Unfortunately, the reality of the economic product cycle is that the market it always clamoring for new features. And/or, if a manufacturer waited until the third iteration, the design cycle would take so long, they would be out of business by the time they were done. (Per my sentence above about how long it took us to build our Glasair. Our buddies were flying theirs in 3, making us wonder if the extra time was worth it.)

Fortunately, software isn't hard to change like hardware. It's probably more user inertia rather than product inertia that would make it difficult to start over with a clean sheet design if and when appropriate. So I think we're stuck at iteration 2.

Still, from my posts on "de-clutter," you can see I've already been thinking about featureitis and anticipating an ever growing and/or growing more complicated GUI. That is, instead of constantly adding new stuff, I've been thinking about removing old stuff. I submit that we should think more about removing old stuff as an incremental path to iteration 3.

Philosophically, I was musing the other day if there will ever be a day when Brian can say of the iFly code "it's finished."

I don't pay attention to ForeFlight. They've been around a long time. Have they reached the asymptote where new features are few and far between?

 
New Post
6/26/2015 1:42 PM
 
Jim_W wrote:
Tinker - That is probable a great suggestion for IFR flying. However, for those of us who don't want to talk to the 'nice man', i.e. - VFR only, this would only add to UI complexity. In order to make everyone happy, perhaps it is time for AP to consider developing two apps - one for VFR and the other for IFR. - Walter? Shane? - Jim Williams

Well, my thought was that one of the things zoom-to-waypoint would do for a VFR pilot is to make it easy to zoom to a specific airport or VOR. (It can be hard to find an airport when zoomed out.) From that point the UI gives him/her lots of options for information and flight planning. Once in a great while, too, a VFR pilot might actually want an "IFR" waypoint. For example, KELSI intersection near Chicago is depicted on the sectionals and it is a handy VFR waypoint for those who want to stay out of the CHI TRACON's hair.

RE UI complexity I agree in principle (obviously) but my suggested implementation/long push on either zoom button really keeps the feature completely out of the way for people who don't want to use it. So I claim innocence on that one!

 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly Wish-ListiFly Wish-List"Featureitis" but still a suggestion."Featureitis" but still a suggestion.