For the last several versions of Ink Calendar I have been focusing on fixing bugs. I am trying to do everything in my power to fix every single instance of crashing and performance issues. Watching every crash in AppCenter and doing what I can to understand and fix the root cause.
Stability ebbs and flows due to me rearchitecting the app to be more robust overall. One major source of crashes in the past month were related to me using a different system for triggering timers. This new system was the modern way of having reoccurring checks for new ink in the cloud and loading and syncing. I have since been able to refine my implementation and have seen crashes reduce significantly.
Another major area of focus has always been memory usage and the speed for views to load. With the next update (2.2.17) I’ll be rolling out a new cache method when switching between views. In my testing this new method is robust and reduces possible memory leaks from switching back and forth between views.
With any new addition like this the risk of bugs being introduced is high. However, the opposite is also very possible. Ideally with fewer objects hanging around in memory doing strange things Ink Calendar should be more stable. I test Ink Calendar on three devices in a variety of different ways. In addition to manual testing I write unit tests to ensure methods are robust and fault tolerant.
Hopefully you’ve stuck around over the years while I’ve been working on Ink Calendar. I want to believe the app has become a great app and delivers way more value to users. As always, I’m open to any feedback or suggestions. Just email support at inkcalendar dot com.