Roadmap and release cycle - iFly General Discussions - iFly EFB

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 General Di...iFly General Di...Roadmap and release cycleRoadmap and release cycle
Previous
 
Next
New Post
4/25/2011 12:56 PM
 

Hello,

I'm new to the forum and considering the 700 as an option.

Do you have a place to let people see what features are planned for the next release or feature roadmap goals?

I understand that not everything makes it into each release and a lot of work can be diverted for bug fixes. But I'm curious to know where you see the product's capability in 6 to 12 months.

Also, what's your release cycle? Is it based on a time frame or a feature set? Should I expect quarterly relaesed or do they come unannounced once you have enough things to call it a good build?

Lastly, what is the base OS of the device?

Thanks much!

-David

 
New Post
4/25/2011 3:55 PM
 

David,

Excellent question. We do not publish specific features with dates; I've been developing software long enough to understand that although sales folks love doing this, in the long run it can lead to busted expectations. But I expect our iFly owners will attest that we're doing a pretty good job of continuing to imporve the iFly, and doing so at a very rapid pace.

This is our process: We determine the best features based on user feedback and development level-of-effort. The feature lists becomes a hybrid of the most important features for our users balanced by development costs. Then we build the new version, and perform QC until we're satisfied with the quality. Then I release the product to beta and let real users test the new release. When the beta testers find bugs or make additional simple suggestions, we implement those and re-release to beta. When the bug fixes stop coming in, we release to production. The entire process typically takes 4 months from start to finish for a major release.

I will announce the contents of a release before it goes to beta. If I do so sooner there is a risk a feature get's pulled last minute, and I really don't want to have to explain that. For example, terrain was actually internally planned for the version 5 release - but at the last minute we discovered issues with our data and had to scrap that feature.

I am happy to give you our high level plans for a release, but I always caveat this with a caution not to take this to the bank...plans can change. We're shooting for a summer release of our version 6 software. The major intended features for this are ADS-B weather, terrain, and geo-referenced approach plates. There will be some other smaller features such as an improved timer and checklists. Because we have 3 huge features slated there is a good chance one of them will slip. And based on user feedback I think ADS-B and Geo-ref plates are more important, so if we need to slip something it will be terrain (again).

I hope that adequately explains our philosophy and where we are today. Version 7 is still in the white-board phase. Some things being thrown about include portrait mode, WAC charts, HSI and other simulated analog instruments.

Thanks!
Walter


Walter Boyd
President, Adventure Pilot
 
New Post
4/25/2011 8:46 PM
 

Being in software development myself, I get used to seeing the roadmaps and having access to scrums.

But, yeah, I appreciate having to manage customer expectations. You can only write so much code in a day :)

Do you have a place where registered members can 'vote' on features? We've found it useful when trying to prioritize (Here's three options, pick the one you need the most).

I'm still on the fence between yours and a few other options and I'm not sure what's going to push me over the edge. Call it buyer's indecision.

Your form factor is near ideal as it's about the size of a folded map. The lack of onboard battery is troublesome tho. I like poking aound with the maps during lunch. That and a multi-use platform is nice around the campfire.

My Dad just bought one for his RV8. Maybe I need to play around with his some first.

Thanks again.

David

 
New Post
4/26/2011 10:06 AM
 

David, yes - you can use the wishlist forum to post feature requests and provide feedback on other requests, or just add your "vote".

Thanks,
Walter


Walter Boyd
President, Adventure Pilot
 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly General Di...iFly General Di...Roadmap and release cycleRoadmap and release cycle