New version of @crashcatch (crashcatch.com) is now available with a completely redesigned user interface making it even simpler to manage your crashes and errors.
Major new version of Crash Catch being installed tomorrow. Been a huge amount of work and I think makes the user interface much cleaner and nicer compared to the current version.
Working on a new landing page for @crashcatch but I can't make up my mind whether I like this part or not. I'm trying to emphasise a portion of the web page without so I've blurred background and enlarged the bit to focus on.
Backend rewrite is all done for @crashcatch. Now working on the migration scripts to copy the data from the old DB to the new DB - think it might take a while to run when I have 1/2 million crashes in the DB.
When I started working on @crashcatch I didn't focus on mobile support as rightly or wrongly suspect that the majority of the time any crash reports would be looked on a desktop/laptop screen so mobile didn't display correctly.
Finally managed to get iOS reporting working for @crashcatch (with a caveat that it doesn't support unhandled exceptions). I'll do a blog post about why. This has taken a lot longer than I had hoped, much more complicated than any other language I've done.
Preparing opening up access for private betas on @crashcatch and while putting it together and doing final testing, found the crash/error engine could crash it sometimes if a ReactJS project submits a crash. Glad I caught that before making that available 😱