Currently working on an important first update to Tusks that will address many of the early pain points/limitations. Should be submitted for App Store review no later than tomorrow night.
There are still important issues under review, such as a crash when signing in to specific servers/accounts :( Need more time unfortunately to get to the bottom of this one.
(Also: It is actually a holiday here in the UK today, so will also get back to the many @’s hopefully later tonight.)
No updates this week, sorry. Another smaller (passion) project had my attention. It’s with App Store Review now. So, regular Tusks service resumes next week!
A productive start to the week. Set up a “performance” dev branch which has successfully targeted three areas of code that were eating up noticeable chunks of memory. Now to more fun work!
Plenty new, improved and fixed in Tusks 1.10. Shout-out to @dnanian who taught me a few magic tricks. As a result, we have a smarter and more capable composer than before. More still to come! #buildinpublic
TFW you find a bug moments before hitting [Release this version]. What do you do? Accept there will always be bugs and fix in the next.
How to avoid this particular bug: on iOS, please only select [Re-order] in the composer if you‘re on a blank/new post. Otherwise the post will be cleared 🤦🏽♂️
The upside of being aware of each post’s root is the ability to highlight actual threads (as well as their length). But not for free. There are more server requests made to get this info. So, must be mindful of any performance hit.
For perspective, that's update #6 since things took off last month. A much better (and more stable) app today. Still ways to go, but feeling good about the future. Thanks to everyone for their continued patience, feedback and encouragement 🙏🏽 #buildinpublic