The following issues are known. Please drop me an email if any other issues are significantly impairing your use of Crickles.
Sign-up process
The sign-up process for Crickles is not ideal and requires new users to wait for the first daily processing cycle after they sign up to run before they can log on. A solution to this is possible if/when I get time.
Device compatibility
Crickles is designed to run on a computer. Operation on a tablet and especially on a phone is not designed for, let alone optimised. I have prototyped a phone app that works quite nicely but don’t currently plan to release it so long as Crickles remains free as it would increase my running costs and time spent on support.
Password/credentials saving
Crickles tries to cache your credentials as cookies so that you don’t need to keep re-entering them between sessions. This usually works best on Firefox. Chrome and Safari correctly save and recall credentials but still require you to hit enter on the log-in screen. Behaviour for individual users on any browser is dependent upon a variety of settings. Users have reported issues on different platforms and with various password managers. This is tough to fix although it might be possible to resolve in a phone app release (see above).