Home
Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New resources
Latest activity
NC Software
Downloads
Help Desk
News
Knowledgebase
Flightinfo.com
Gallery
New media
New comments
Search media
Resources
Latest reviews
Search resources
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
APDL and Logbook Pro for Android are now in public beta.
Click here
to join the public beta and install the latest versions today.
Home
Forums
API
Logbook Pro API
Welcome
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Neal Culiner, post: 21500, member: 1"] Diedrich, Let's take for example there is a mobile logbook app "Acme Logbook" or even a web logbook "Acme Web Logbook". We have users that use other logbook products but want to use the power of Logbook Pro such as the Analyzer, Reports, or other features they may need not available in a product they use. With the Logbook Pro API the vendor of that app can build an integration where the user could tap a button such as our "Sync" button in our Logbook Pro apps and that mobile data can be sent to the cloud via our service where Logbook Pro Desktop can pick it up. Before we had our Logbook Pro iOS app we recommended our users check out a nice little app called Flogger which had a Logbook Pro integration via google documents and other export methods. Other mobile apps that are standalone have an export or e-mail CSV option and then the user can import that data into Logbook Pro Desktop, their Windows logbook of choice. Again in this scenario any logbook vendor can port their data to Logbook Pro via our service oriented architecture. This is not just mobile, it could be any other logbook product on any platform: Windows, Mac, Web, Mobile. Another case is we don't have BlackBerry support nor intend to produce one. Maybe someone else does, or Windows Phone 7 as an example. We can empower the developer community by allowing all of those other apps out there work with our growing services. We have the most advanced schedule importer ever. It's an extremely complex and expensive system to create and maintain. Any user can use our schedule importer to parse their trips and store to their cloud account. Other apps can leverage our system to then bring that data to their apps over the cloud. We already make export options available such as to TAB and CSV but the cloud system is far less effort and more seamless. We'll start off small and go from there. We have a fantastic infrastructure and architecture we built over the recent years and now it's time to really start to put it to use among other things we have in the works that this was designed for. Does that make sense? [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
API
Logbook Pro API
Welcome
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top