It's progressing, just more slowly than I'd like - I'm a student and it's finals week, I'm afraid that comes first. Of course, the week after finals I have nothing but free time...
yea, yea...I know I'm no where like you other pilots, but, us Balloon pilots and crews also need to log their flights.... Pilots for FAA reasons and crews for ensuring they are getting paid for their flights.
I think the pilot log book is great...but, I think a separate application may be needed for my purposes... Anyone interested, let me know! I don't have the vast requirements as a big commerical pilots do, but there are a few.
My suggestion to the people out there who are thinking of creating an android pilot logbook program: don't try to reinvent the wheel. There are already a lot of logbook applications out there which a lot of effort has been put into, and are quite feature rich. No offense or anything, but it's not likley that you can better some of these other projects out there with a dinky little android app.
Instead try to leverage the advantages of the android platform by creating something those other applications can not do. Maybe have your android app be a portable front end to other more polished pilot logbook software. Get in touch with some of the authors of the other logbook software projects, maybe work together on something.
My suggestion to the people out there who are thinking of creating an android pilot logbook program: don't try to reinvent the wheel. There are already a lot of logbook applications out there which a lot of effort has been put into, and are quite feature rich. No offense or anything, but it's not likley that you can better some of these other projects out there with a dinky little android app.
The Android app certainly does not need to have all the capabilities of polished PC-based Logbook packages, but it still needs to have basic functionality to capture/present the logbook information.
Quote:
Instead try to leverage the advantages of the android platform by creating something those other applications can not do. Maybe have your android app be a portable front end to other more polished pilot logbook software. Get in touch with some of the authors of the other logbook software projects, maybe work together on something.
Unless one is integrating the Android app with an online web/services based Logbook application, the Android app will need to exchange data or sync with the Logbook application when the user heads back to base.
Reporting and other fancy import/export features can be done in the backend Logbook application (on a bigger screen!).
This may become a headache for the Android developer - really just shifting the Android frontend development (under the developer's control) work to backend integration work (less controlled and maybe impossible if the other parties do not want to open up).
A bunch of other questions ... Which packages to integrate with? What are the popular ones? Are they open, or do we need to integrate differently for each one? Is this actually making the Android app more difficult and time consuming to develop? ...
The Android app certainly does not need to have all the capabilities of polished PC-based Logbook packages, but it still needs to have basic functionality to capture/present the logbook information.
Unless one is integrating the Android app with an online web/services based Logbook application, the Android app will need to exchange data or sync with the Logbook application when the user heads back to base.
Reporting and other fancy import/export features can be done in the backend Logbook application (on a bigger screen!).
This may become a headache for the Android developer - really just shifting the Android frontend development (under the developer's control) work to backend integration work (less controlled and maybe impossible if the other parties do not want to open up).
A bunch of other questions ... Which packages to integrate with? What are the popular ones? Are they open, or do we need to integrate differently for each one? Is this actually making the Android app more difficult and time consuming to develop? ...
As I stated earlier. All we need is for this app to export to CSV. Logbook pro will import CSV. Problem solved.
From what I've been reading and what I know what I'd want, it sounds like the best app would be a simple data entry app to a DB backend that can later be exported to a CSV file and uploaded elsewhere. One can make settings to choose what external system they wish to export to which would drive how the data is extrapolated... Maybe a location-based collection entry for TO/FROM fields (with manual override) and a few additional selection/dropdown fields.
It might be easier to start on a very simple app and add to it piece by piece. Get the basics down and continue to build on it.
Some great ideas here...just need to start putting it into code. I wish I knew how to do it myself!
From what I've been reading and what I know what I'd want, it sounds like the best app would be a simple data entry app to a DB backend that can later be exported to a CSV file and uploaded elsewhere. One can make settings to choose what external system they wish to export to which would drive how the data is extrapolated... Maybe a location-based collection entry for TO/FROM fields (with manual override) and a few additional selection/dropdown fields.
That would put a reasonable scope for the app. But still, even for the front-end, it will take some effort/care to produce a user-friendly interface.
Quote:
It might be easier to start on a very simple app and add to it piece by piece. Get the basics down and continue to build on it.
Some great ideas here...just need to start putting it into code. I wish I knew how to do it myself!
So, what are your requirements for a Balloon Pilot Logbook? Did anyone actually contact you?
That would put a reasonable scope for the app. But still, even for the front-end, it will take some effort/care to produce a user-friendly interface.
So, what are your requirements for a Balloon Pilot Logbook? Did anyone actually contact you?
I would tend to agree...the user interface is most important.
No has yet contacted me - so, let's go with the very simple and consider the following fields:
Date - (MM/DD/YYYY)
Time - For Balloons, it's AM or PM. Actual time doesn't matter.
Balloon Information
- Make
- Model
- Balloon N#
Flight Information
- Launch Site (if done right, this could pull current GPS location)
- Landing Site (if done right, this could pull current GPS location)
- Distance
- Max. Altitude
- # Passengers
- # Landings
Wind Data (all drop downs selections in increments of 1 or 2 knots)
- Speed at Take Off
- Gusts
- Speed at Landing
Remarks, Procedures, Maneuvers - Free text field
Piloting Type Time - each with numerical entry (XX.xx Hours)
- Free Flight
- Tether Flight
- Instruction Provided
- Instruction Received
We could go one step further and allow the balloon type be configurable in that the user preconfigures the Balloon Information section, provide it a name (balloons are all named) and then make it selectable in a drop down or what ever is easiest as opposed of having to enter the information each time.
Even easier than this would be a Balloon Crew Log with the following information:
Date/Time (AM/PM)
Company
Balloon
Pilot
Launch Site
Land Site
Comments
Paid Y/N?
""Thank you for your inquiry. I don't want to mislead anyone so I'm going to be honest and up front so you know exactly where we stand. Logbook Pro 2010 is our priority development effort, as it is now, it probably won't be ready until this fall at the earliest. We are working on the iPhone app now, Android I'm not sure when that's coming. It may not be until after Logbook Pro 2010 releases so I don't foresee it coming in 2010. Android is not our priority at this moment."
From what I've been reading and what I know what I'd want, it sounds like the best app would be a simple data entry app to a DB backend that can later be exported to a CSV file and uploaded elsewhere. One can make settings to choose what external system they wish to export to which would drive how the data is extrapolated... Maybe a location-based collection entry for TO/FROM fields (with manual override) and a few additional selection/dropdown fields.
It might be easier to start on a very simple app and add to it piece by piece. Get the basics down and continue to build on it.
Some great ideas here...just need to start putting it into code. I wish I knew how to do it myself!
I'm a private pilot flying a Cirrus SR22. I use Logbook Pro for my flight data. It's easy to enter the data into an excel spreadsheet (documents to go) and then dump it into Logbook Pro as stated below from Logbook Pro's WEB site:
"Logbook Pro imports using a custom Import Wizard within the software. If you can get your data into a program such as Microsoft Excel (which should read ODBC...) format it as close to the Spreadsheet Style logbook as possible. Then click File...Import to import your data. "
So, was someone actually working on something or were we all just talking amongst ourselves?
I agree that a Document to Go Excel spreadsheet is easy enough and the output to a PC-based logging environment is a great idea....I would still be interested in seeing what could be done for an Android-based logger that has a custom interface. It's always more fun with a cool interface!
A pilot friend of mine brought this to my attention...I might be interested in giving this a shot, just have to pitch it to my partners. The biggest problem is the threat of competition - such as the iphone developer writing an android application. Also there is the looming issue of how big or small the market really is.
How many downloads does the iphone app have and how much does it cost?
Hello. New to the forum and getting a New Android the end of the week. Been looking around for a good Logbook. What you have developed looks very promising. Would also like to try it out if possible. I am a professional pilot flying about 85-90 hrs a month
Thanks.
Thanks everyone for your interest and patience. It would probably be a few more days before both apps are released for testing.
When you send a private message to register your interest, please include information on your handset, Android version, the countries you fly, whether you're a commercial/private pilot, and your company (if you wish to disclose).
Sorry for the delay. This first version is now ready for testing.
Pilot LogBook (IntelliPilot v0.1) - Screenshots
Requires Android 1.6+
Developed for pilots, this app can capture details on flights, aircraft, etc.
V0.1 features:
- Capture flight and aircraft details
- List flights and aircrafts
- Include 5000+ ICAO airport codes
- Autocomplete for airport codes and aircraft rego#
- Primitive export
V0.1 known bugs:
- Autocomplete for rego does not return unique values (will not be required in v0.2 with the rego database)
v0.2 features (planned):
- Improve export
- Add rego database for planes
- Capture details for other crews
- Include summary page of hours
v0.3 features (planned):
- Add support for IATA codes
- Handle both local and UTC times
v0.x features (being considered):
- Support user-defined custom fields
- Auto lock records to prevent accidental changes
- Auto enter pilot times
- Allow a return flight to be created
Balloon Pilot LogBook (IntelliBalloon v0.1) - Screenshots
Requires Android 1.6+
Developed for balloon pilots, this app can capture details on flights, balloons and launching/landing sites.
V0.1 features:
- Capture flight, balloon and site details
- List flights, balloons and sites
- Integrated with Google Maps
- Integrated with GPS
- Primitive export
V0.1 known issues:
- Have to turn on GPS before use and off after use manually
v0.2 features (planned):
- Improve export
- Improve GPS integration
- Include summary page of hours
Last edited by lenchan; April 27th, 2010 at 09:07 AM.
Reason: Update planned features
The Following 6 Users Say Thank You to lenchan For This Useful Post:
I'm a professional pilot flying around 90 hours a month. I would love to test or purchase any android logbook in development. I've been searching for a while now. How can I purchase it? You can email me at Ericreed22@gmail.com. Thank you.
Lenchan, ur app Is excellent! I also like ur plans for future apps. If I may I'd just like to leave some feed
back..
Firstly, the hours that are calculated need to be In houris and minutes instead is a decimal but I'm sure u planned that already..
Also would be great if when the times are inserted, the total is copied to the clipboard so It can be pasted into the right box.
Also.. some airlines use whats called factorised hours, Which is a percentage of the hours flown whwn there r3 or 4 pilots instead of 2. My company calls this factorised hours or FTL. And we use 85% for 4 pilot operations and 90% for 3 pilot ops. Would It be possible to have another box for FTL where you could choosea percentage of the total flight time? Thanks. Will give u more feedback on ur next version.
Hope I'm not overwhelming u.. just giving suggestions. Thanks again Lenchan for ur great work..
Firstly, the hours that are calculated need to be In houris and minutes instead is a decimal but I'm sure u planned that already.
Noted. Some people like hh:mm and some like decimal hours. Still thinking what to do
Quote:
Originally Posted by Dunebug
Also would be great if when the times are inserted, the total is copied to the clipboard so It can be pasted into the right box.
Can you provide an example please to show the intended result/effect. Some people have suggested some form of auto entry of piloting times.
Quote:
Originally Posted by Dunebug
Also.. some airlines use whats called factorised hours, Which is a percentage of the hours flown whwn there r3 or 4 pilots instead of 2. My company calls this factorised hours or FTL. And we use 85% for 4 pilot operations and 90% for 3 pilot ops. Would It be possible to have another box for FTL where you could choosea percentage of the total flight time?
Ok, do you just want a field to capture this %, or you want some calculations to be applied as well. There will be support for user-defined fields in future test releases - maybe that will solve this problem if you don't need any further processing?
Quote:
Originally Posted by Dunebug
Thanks. Will give u more feedback on ur next version. Hope I'm not overwhelming u.. just giving suggestions. Thanks again Lenchan for ur great work..
Thanks for your feedback. All suggestions are very welcome, and we're prioritising requested features, so we won't feel overwhelmed
Also, expect v0.2 to come out in the next few days
Noted. Some people like hh:mm and some like decimal hours. Still thinking what to do
Hi lenchan, as i already told you, me too prefer to have hh:mm format
Anyway, is very difficult to implement both?
Quote:
Can you provide an example please to show the intended result/effect. Some people have suggested some form of auto entry of piloting times.
I believe that auto-entry could be done for PIC/FO time, IFR (in case of airline flying) just having some sort of "option" that count the whole time as "a kind" (count all my time as "FO" and "IFR" unless i manually change it)
Quote:
Thanks for your feedback. All suggestions are very welcome, and we're prioritising requested features, so we won't feel overwhelmed
Also, expect v0.2 to come out in the next few days
Waiting for it, the app looks very good even at this early stage
I believe that auto-entry could be done for PIC/FO time, IFR (in case of airline flying) just having some sort of "option" that count the whole time as "a kind" (count all my time as "FO" and "IFR" unless i manually change it)
I would love to see a way for all the total times to be reflected on my android device. For example, PIC, SIC, jet, total time, etc. Other then that, it's a great app...... Looking forward to the update 0.2.
I have used the app for a few weeks now. I like it a lot already. For improvements I agree with people who prefer the hh:mm format.
Auto entry for the hours would be nice as well. Default to day for example and if you put anything in the night box it should adjust the day hours.
Other that that, some kind of query function where I could see hours flown over the last 6 months for example or the last year, would be a nice implementation as well.
Thanks for all your good work. As far as I know you are the only one so far with a workable app.
I have used the app for a few weeks now. I like it a lot already.
Thanks for your testing and feedback.
Quote:
Originally Posted by Peteram
For improvements I agree with people who prefer the hh:mm format.
Working on accommodating both hh:mm and hh.x :-) Due to the time constraint, we may have to settle for one first for v0.2.
Quote:
Originally Posted by Peteram
Auto entry for the hours would be nice as well. Default to day for example and if you put anything in the night box it should adjust the day hours.
Many testers are interested in auto entry so we're bringing this feature forward to v0.2. Different testers have quite different views of how they want it done, so the v0.2 implementation is perhaps an initial attempt.
Quote:
Originally Posted by Peteram
Other that that, some kind of query function where I could see hours flown over the last 6 months for example or the last year, would be a nice implementation as well.
We'll have a (preliminary) summary feature in v0.2, and a more sophisticated one with custom query/range in v0.3.
The current implementation of the summary function is like this.
Quote:
Originally Posted by Peteram
Thanks for all your good work. As far as I know you are the only one so far with a workable app.
Thanks for your feedback.
BTW, it seems that a long time has passed since we released v0.1, but I just realised that it was only 2 weeks ago! :-) Originally, we planned to have v0.2 out by now, but we have decided to bring forward some v0.x features plus some other user requests to v0.2, so we're a bit behind.
It looks like that we'll stretch the schedule out for one more week, but for those who are eagerly waiting, v0.2 should be an interesting release.
In the meantime, please continue your testing and feedback.
Last edited by lenchan; May 10th, 2010 at 07:17 AM.
Reason: Typo
...
We'll have a (preliminary) summary feature in v0.2, and a more sophisticated one with custom query/range in v0.3.
The current implementation of the summary function is like this.
Amazing!!!
Quote:
Thanks for your feedback.
BTW, it seems that a long time has passed since we released v0.1, but I just realised that it was only 2 weeks ago! :-) Originally, we planned to have v0.2 out by now, but we have decided to bring forward some v0.x features plus some other user requests to v0.2, so we're a bit behind.
It looks like that we'll stretch the schedule out for one more week, but for those who are eagerly waiting, v0.2 should be an interesting release.
In the meantime, please continue your testing and feedback.
Thank you so much for the time invested in that...
Can't wait to see the next release. The summary function looks really good.
Another suggestion I would like to make, is to be able to customize the hours input. For example I don't really care anymore whether my hours are day or night. Some hours I act as an instructor in a simulator and there is no input for that right now. I am using the "instruments" column for that right now. Be nice if I could rename that. Instrument is not something I log seperately anymore.
Can't wait to see the next release. The summary function looks really good.
Thanks, the summary screen has changed a bit since I posted the screenshot. Anyway, v0.2 is progressing quite well, and it should be out real soon
Quote:
Originally Posted by Peteram
Another suggestion I would like to make, is to be able to customize the hours input. For example I don't really care anymore whether my hours are day or night. Some hours I act as an instructor in a simulator and there is no input for that right now. I am using the "instruments" column for that right now. Be nice if I could rename that. Instrument is not something I log seperately anymore.
Do you need just a single field for capturing the instructor time? Do other people need to capture day and night instructor times?
v0.3 is expected to have support for custom fields, so you can define a custom time field called "Instructor Time" to capture that.
