Quote:
Originally Posted by robn
BB 10 has a fairly competent CalDAV implementation that works fine with our servers. Was there a reason you couldn't use that, or did you mean something else?
|
Thanks for your response. I did create the calendar on the BB, but there were two points of dissatisfaction. These can be "blamed" on BB, if you like, and maybe you're right. From my perspective, all that mattered was that the service didn't work the way I wanted it to. Or maybe it was my own mistake, in which case I don't mind being corrected and would even request that my FM trial account be re-opened so I can try it again.
The first problem was that the Fastmail calendar didn't really sync with the BB calendar. They were both available on the BB, but not merged. So if I wanted to create an event that would be saved to both calendars, I'd have to do it twice, switching between the two views to do so. That's not what I want. I want the calendars to actually be synchronized so they are both the same. But I want them both to exist separately, as well -- just identically.
My reasons for this have to do with the fact that I live in a rural area where cell service is spotty. I can always create appointments on the BB local calendar, but I can't always create appointments on a third-party calendar. What I want is to be able to create a local appointment which will then automatically sync with the remote calendar when I pass through an area where I have a signal. I also want to be able to check and make changes to the remote calendar using a computer, and for those changes to sync back to my device when it grabs a signal. I want true synchronization, not a second calendar that happens to be available on the BB.
The second problem I had is really a BB problem, but it's one that could be overcome with a native app. The BB's shortest-allowable sync interval is 12 hours. That's not what I want. I want instantaneous if the device currently has a connection, or immediately upon getting one if it doesn't. A native app could do this.
As for the Android app via Amazon, I'm not interested. I don't want to constantly virtualize a second operating system on a phone just to sync a calendar. I'm also a bit leery of anything built for Android simply because I detest Google with a passion (else I would just use their Calendar) and would need to be sure that Google wouldn't be able to glean even the slightest bit of information about me by way of the ported app. And even then, the performance hit from virtualizing the Android OS would remain a drawback.
I hope my explanation makes sense to you. If not, please let me know and I'll try to clarify. Or if there was something I could have done to make your service work like I want it to, feel free to correct me and I'll give it another go. I have no delusions of omniscience about BBs or anything else.
One more note: You seem to feel that BB users are such a small share of the market that we're not worth coding for. Your opinion, however, ignores three factors:
The first is that there are users who do use the ported Android app, who probably show up as Android users on your radar.
The second is that BB users tend to be very loyal, so almost certainly if you put out a well-functioning, native BB app, you would get new paid users (including, as a certainty, myself).
The third is that BB seems to me to be regaining some popularity, especially among business users who need a tool, not a toy; as well as among users who hate Google so much that if Android were the last phone OS on the market, we'd switch back to land lines. (I happen to fall into both groups.)
Thanks again for your response. I appreciate it. I hope my explanation does justice to your interest.
Richard