I do understand...

[Alphacodex]

I read alot of bashing about the recent 1.0 Agendus fpr iPhone. I can understand them because it also buggers me like hell, that there is no acceptable calendar-solution for the iPhone yet. Of course as soon as I heard abaout Agendus for iPhone, that rose a lot of expectations ...

But we must understand it's not Agendus - it's apple to place the blame. They don't allow developers to use the internal database. A standalone database would be a quite bad workaround. I'm not sure if I would be lucky with such a solution...

I can perfectly understand the strategy of iambic (although I'm also very disappointed with the actual features of Agendus 1.0)
-> It's to put as many features into Agendus as they can with the actual SDK and prepare everything to launch the calendaer functionality as soon as they can access the internal data. By the way: If I buy Agendus now, will I get the calendar update for free as sson as it gets into Agendus??

We should maybe flood the apple forums, asking for opening up the calendar API, rather than flaming around here at iambic - they just can't change it...

However if nothings else works - I would vote to support jailbreaked iPhones...


Greetings
Codex

[michael]

Hi Codex,
Thanks for posting your feedback, and especially for expressing your understanding of our position on the lack of a calendar in AGiPH 1.0. We are still investigating what possibilities we might consider until Apple allows access to the Calendar, so hopefully we'll have some sort of solution soon.

AFAIK (at this point in time) there will not be an additional charge for when we add a calendar solution. Of course it all depends on what our investment turns out to be to plan/develop/implement/market. Our goal would, of course to not require anything if financially feesible.

Thanks again.

[Sulley]

AlphaCodex,


I absolutely understand that the problems of how to handle calendaring are not iambic's fault. It all lies with Apple (and what they do and don't allow access to). The problem is that iambic will not know if/when Apple will ever provide APIs and access to the Calendar app data and a solution has to be found, even if it is a temporary and not the best one.

I've been one of the biggest "mouths" on here with concerns about the calandering situation. It's because I have been a customer since almost the beginning, I have a desire to be able to stop using my Palm (which sole purpose is to run Agendus), I've bought the $8 app from the App Store, and I want iambic to do well and smash the competition with the real Agendus! I want it to be the best product in its category on the AppStore.

Read the new sticky note that Adriano posted a bit ago. It sounds like they've taken a stance on calendaring, especially, and explained where they're at on task syncing.

Take care!

[facrowe]

:) Happy to see Adrino's post.

The built in calendar is useless anyway. I have never used it because of its many limitations.

Until Apple opens up, building an integrated calendar with full agendus functionality will blow away the competition.

I'm still using my Palm T3 because of agendus.

Looking forward to iPhone version that integrates dialing, to-do, calendar, and contacts and hopefully daily journal.

[armejia]

Hi Codex,
Thanks for posting your feedback, and especially for expressing your understanding of our position on the lack of a calendar in AGiPH 1.0. We are still investigating what possibilities we might consider until Apple allows access to the Calendar, so hopefully we'll have some sort of solution soon.

AFAIK (at this point in time) there will not be an additional charge for when we add a calendar solution. Of course it all depends on what our investment turns out to be to plan/develop/implement/market. Our goal would, of course to not require anything if financially feesible.

Thanks again.

Good to hear this. :)

[Alphacodex]

...and to show my loyality I bought that early and quite buggy Agendus 1.0 for my new iPhone hoping I did not bet on the wrong horse... ;-)

However I do have one question. In the moment, if I want to use the "groups" functionality within the iPhone I have tosplit my contacts in Outlook in multiple Adress-Books. Will Agendus use the same route ("one group is one adressbook") or will it bring back some sort of categories as on the palm?
You can imagine, I do not want to do all the work twice - splitting up all my contacts, and then merging them again, assigning them to different categories...
By the way: I would vote for using the native iPhone style: one adressbook = one group, so the other apps will walk in line...
(Having said that, I'm missing the feature to move a contact to a different group within Agendus 1.0, and I can't change the colors of the task-groups, and the font in the contacts view looks sorta blurry)

Same applies to calendar, as soon as it'll be in: one calendar is one group-approach or one big calendar with different category-tags assigned to every assignment?? I'm thinking about splitting up my calendar, so I can use the different colors within the iPhone Calendar...

Thanx!
Codex