[Android Apps and Games] CaptainStarbuck:
@ajige - I've been DanG's TDL on and off for years and am glad that you took this initiative. Thanks. While I've had your Android app loaded and updating since the start I have only now had time to really start experimenting with it. :rolleyes: Here are some random thoughts:

I know you've been asked about open sourcing your code. I'll add a +1 on that, only because you seem to be doing this as a community service and labor of love, not as a for-profit endeavor. I'm only a casual Java developer, primarily a C# guy. But I have been trying to get my feet wet with Android development and this would be one way to do that with a project that I'm motivated to work on. So if you decide to FOSS this code I will certainly try to find some time to poke at it.

As a C# guy, I'm looking at Xamarin as my "vector of approach" into Android development. This allows me to use C# and Visual Studio while still coding to Activities, Intents, etc. Knowing you're doing Windows Phone development, I'm wondering if you would consider the current v1.4 release to be more of a prototype, and re-starting this project with Xamarin. (I really wish TDL was written in C# instead of C++ but it is what it is.) One benefit there is that "most" of the code set is portable to Android, Windows Phone, and iPhone. Everyone wins. :victory: (except maybe people who really want to do this all in Java...) Unfortunately Xamarin has a price for production apps (free for emulation-only development).

I think the priority should be toward getting as much compatibility as possible with

fields

supported by TDL, and not with UI nuances. In other words, mimic what TDL does and no so much how it does it. We all love the TDL desktop app and moving data between mobile and desktop would seem to be everyone's priority. I see UI nuances as a diversion unless there are real bugs. Even if fields aren't supported yet for modification or even display, I think data should flow in both directions with zero disparities, and no chance of loss in transit. When we have this, display becomes a nice enhancement, changes to display aren't so critical, and updating fields becomes a natural and welcome progression.

I did a search on "Gantt" in the Google Play (Market) and this app did not come up. I highly recommend adding "gantt" and "gantt chart" to the keyword list. Anyone looking for project management should be able to find this app quickly.

Ultimately I would love to be able to use Time logging apps to log time against tasks in TDL. The synergy is obvious. What's lacking is a common API for sharing clients, projects, tasks, Allocated To individuals (contacts), and time logged. When this app is more mature I think it would be a real bonus to see some of these time clock apps claiming support for TDL integration. The usage of this app would explode as would awareness and usage of the desktop TDL, Gantt Project, etc. But that's for a little later. :eek:

About the app itself:

For some projects I tend to follow a consistent pattern. Like for writing code we do specs, get approvals, write code, write docs, do QA, beta, process feedback, then do a production release. (Details omitted and order not important, you get the idea). With the desktop version of TDL we can Copy/Paste nodes. With Android we can only Cut/Paste. So despite what I said about UI changes ;) I think this is important.

Finally (aw, so soon? :cyclops:) - I immediately found that without Dependencies that my first list(s) couldn't really be used for anything other than testing. That's just me of course but note from the above that tasks must be done in a specific order. For now I'm just using Priority to sort them.

That's enough outta me. Regards...