Much like Appy Weather before it, this was a sensitive project. I wanted to completely rebuild the app’s foundations and improve its UI/UX, but without upsetting existing users who are, understandably, set in their ways. Why am I so confident? Because I’ve heard from only a handful of users who weren’t completely sold on every change. The vast majority updated without a peep — a seamless transition. That’s a win in my book.

To learn more about the update, read all about it here.

With this work now done, the weight of legacy code has officially been lifted, freeing me to focus on new projects. Among the first will be bringing ruff — and Appy Weather — to iOS. Neither would have been possible without these rewrites and — more specifically — the move to Kotlin Multiplatform. There are also a couple of other new projects I’m excited to share with you even sooner. Exciting times ahead!

Bardi

I have a number of things to share with you in upcoming episodes, but we begin with the app that has shaped so much of my journey: Appy Weather, of course.

Its long anticipated rewrite — redesign too — finally went live in January. Its brand new website tells the story behind it. Whatever people loved about the original, I doubled-down with v2. It’s bigger, better, and, perhaps most importantly, far more reliable and performant, rebuilt on a modern Android stack: Kotlin code and Jetpack Compose UI.

If you’re still on Android, and stopped using Appy Weather at some point in the last few years, I totally understand why. But please consider giving it another chance: download Appy Weather 2 from Google Play. If you know someone who might enjoy it — a friend, family member, colleague, or follower — spreading the word would mean a lot too.

(There is a subscription, but for the first time — and limited to the first 1,000 people — there is a lifetime unlock for anyone who wants the best value and support its ongoing development.)

If you’re reluctant because you think it’s only a matter of time before the next development hiatus, I get it. But, please note, since its relaunch, there have been a lot of updates with a more inclusive and transparent feedback loop too. Regular development service has resumed, and this time, I have no intention of slowing down or taking any breaks.

I appreciate Appy Weather more today than ever: what it provides me, and what it means to its users. So if you come back, I’ll do everything I can to make sure you won’t regret it.

(For those of you on iOS, there is good news too: I’ve started work on its client and hope to have more to share later this year.)

Speak more really soon.

Bardi

This headache aside, I would really appreciate support for the thing I’ve been mainly working on lately: timing.is — your calendar reimagined. It will be revealed on Product Hunt next week. It would mean a great deal if you can:

1. Go to https://www.producthunt.com/products/timing-is

2. Hit [Notify me]

3. Sign up if you’ve not got an account already.

And next week when it’s revealed, you’ll need to upvote from the notification link you receive.

That’s it! The whole process shouldn’t take up more than a minute of your life, but can — if there’s enough support — make a big difference to my life.

Competition is fierce every day. Whether the launch is successful is disproportionately skewed to how many votes it has in the first few hours. Getting as many early upvotes will go a long, long way, so please get yours in first thing. Our ability to generate signal will also be meaningfully improved if you can share within your own networks too.

Thank you so much for your continued support and interest.

I’ll try not to be a stranger.

Have a great end to your week.

Best,
Bardi

Remember me? It’s Bardi, of course – developer (and occasional author).

Where have I been? Good question!

Last year, I managed to push out a weekly update to the newsletter for 50 weeks in a row. It was a therapeutic finish to every week. But after 50 sessions, I had enough therapy. I needed to ship. So, I began this year intent on prioritising results over the process. Approaching six months later, there’s been a lot of progress on the goal, but – unfortunately – I still have nothing to show for it (: 

Appy Weather continues to be rewritten, but for the past few months, my focus has shifted completely to t:m:ng. Yep, that’s the secret project I teased about ~18 months ago. It’s your calendar re-imagined, built for you and not the enterprise. This one is the closest to the finish, and I’m hopeful for a summer launch. If you’re on iOS, I recommend you sign up to the wait list. It’s the first time I’ve partnered with someone on an app. It’s been so much fun, and we expect it will show in the final product. We’re entering a hot space but we feel we have a point of view that will help set it apart from the competition. I have a 100% record so far and I’m confident I’ll keep the streak going with release #3. 

To be clear, Android and Appy Weather in particular are still a major consideration. They’ve just stopped being the immediate highest priority. I had such big plans for its v2. But I’ve recently accepted that I must majorly scale down its ambition in order to facilitate a finish (otherwise I fear it will easily become a 2023 project). The minimum acceptable output is effectively the current app rewritten with no new major features. Both on iOS and Android. That said, getting these out in 2022 will still be a challenge. Time (and kids) will tell.

I hope to write to you again at least a few more times this year. When I have something meaningful to share. Thanks for your continued interest and support in what I do. It takes time – because I’m built this way – but it’s historically been worth the wait. To the next one!

If you have any questions on t:m:ng, Appy Weather 2 or anything else, hit reply.

Best,
Bardi

After two years, we’re visiting family. For the first time in probably that long, I haven’t even thought about writing a single line of code. Even more foreign is how I don’t feel remotely bad about it (I’m the character who feels guilty when I force myself to Netflix over Xcode on any given evening). I don’t know whether I’ll relapse at any point in the next three weeks. Regardless, I have a good feeling that when I’m back in the New Year, I’ll be at 100% – something I’ve clearly not been for some time – determined to deliver on 2021’s promise.

Have a great week! Hope you all have a relaxing end to the year, surrounded by the people who matter most.

Best,
Bardi

It’s been an expensive end to my year. New (standing) desk, new (4K) monitor, new (14” Max) laptop. That’s around £4k in new gear. I’ve managed to make back > 50% selling what they replace. All in all, not bad business considering I expect the combination to meaningfully boost productivity. The M1 Max MacBook Pro in particular has been a revelation for a few reasons:

1. I can actually work on the couch again in the evenings because the battery doesn’t leak and my thighs don’t fire up. It’s enjoyable too because of the smaller form factor (I’m technically downgrading from the previous 16” Intel Mac).
   

2. Performance is incredible, even on battery. Building a project is so fast that I have no reason to momentarily switch to Safari. Sounds like a silly thing to write, but the difference just several seconds make shouldn’t be underestimated.

I still haven’t received the desk, and won’t set up the monitor until I have (I’m weird like that). I’ve found that there are consistent periods during the day when I’m struggling to get going, usually in the mornings these days. If the desk’s standing position manages to reduce this lull period by just 50% even, then it will make a big difference and would have been money well spent. Plus my back. I’m upgrading from a 2K 25” monitor to a 4K 27”. Hopefully that’s enough additional room to enable more focused sessions on the single screen (laptop in clamshell mode). As the desk is 20cm longer, this would mean I can use my mechanical keyboard again too. I expect the full setup to be in place at the start of the New Year. Can’t wait!

Have a great Sunday!

Best,
Bardi

P.S. on the topic of focus, I can’t believe the year is 2021 and neither MacOS or Windows allow you to have different Docks/Taskbars per virtual desktop.

At least half of my iPad’s value is unlocked through the Apple Pencil. As far as I’m concerned the iPad is the companion accessory. For the last year, I’ve tried out numerous apps to ideate in freeform. Originally, I thought a blank white infinite canvas was what I was looking for. But the lack of boundaries made things become a mess quickly. And although prioritising my content over the app’s chrome puts it in focus and is arguably optimal in certain contexts (imagine you could only write in Word in its reader mode), it became apparent that I have an inherent bias towards less because of the designer in me. This would result in a clean, minimal outputs that look great in screenshots but their everyday utility was compromised because it was work to make the app work. No to a button – let’s dump everything into this menu. No to having a visible drawer that will reduce vertical content by 30 pixels – let’s hide it behind a swipe. Etc.

I came across GoodNotes recently – an important find that will be a big influence on the next generation of Third Culture Apps. Instantly it was clear their developers were not motivated to build the prettiest, most modern piece of software. They wanted to create a note-taking app you would admire not for its aesthetic but its utility. I mean it has an actual toolbar that’s fixed in place. It looks old fashioned but damn it works. My first instinct (and most others’ I suspect judging by other apps I tested) would be to have a single button within to switch between the thickness levels. But they have three! Same applies to colour. I continue to use it everyday because it prioritises my speed and not a designer’s ego.

Last week I had an idea. I built it, and it was pretty much what I had in mind. But the mind can play tricks on you. There were many elements in Appy Weather’s initial release that were unnecessarily clever. Most users didn’t appreciate it because most didn’t get it. Huh? I didn’t know I could… Who was I trying to impress? This idea I had fell in this bucket. So I scrapped it. And went with the simple obvious option: visible tabs on the Forecast screen to switch between Hourly, Daily, and Timeline. It just works. I can unashamedly confirm 2.0 will have a more dense UI than its predecessor. The challenge is to somehow keep things feeling clean. To make more feel as little as possible.

Have a great Sunday!

Best,
Bardi

P.S. “Keep Going” is available this Black Friday for 66% off! It’s made $150 during the promotion so far. I hope to use the funds generated to finally purchase a Fully Jarvis (I’ve had an eye on it for some time and with it being 20% off this month, it’s a case of buy it now or next November). I’m still short by a few hundred dollars but hope to make up the gap as much as possible in the next few days. A better back = more productive days = faster releases in 2022.

Appy Weather 2 started the week with five tabs:

1. Timeline

2. Forecast (Hourly, Daily etc.)

3. Radar

4. 🤐

5. 🤐

But it ends the week on four. Technically one more than the existing version, but when you consider the radar is currently accessible from a FAB (floating action button), then it’s a tie really. That’s impressive considering it will retain all screens from 1.0 but manage to add two entirely new ones. How’s it possible to fit in more within the same screen estate? Without it becoming a bloated mess. Well, craftsmanship doesn’t happen quickly. A lot of thought was put into it. And I mean a lot. The Timeline on its own will essentially integrate all existing screens besides the radar (for the time being, but there’s every possibility it may make the cut too if I can figure it out). Animations play a huge part in this deal. This is another concrete example of a scenario where SwiftUI has empowered me to build a UI that I wouldn’t have even remotely considered otherwise. That said, I’ve only sketched concepts so far. Although it’s theoretically promising, I can’t be certain the current vision has actually strong legs. I’ll find out next week. I’ll let you know.

Have a great Sunday!

Best,
Bardi

Last week I touched on how work on the un-announced project has had an impact on Appy Weather’s development. Let me elaborate. A couple of weeks ago I finalised the system that allows an Appy Weather card go full screen. One card could be selected at a time. To open another involved first closing the selected card. A week later, the secret project had more requirements: 1) for the selected card to be one in a set and 2) to be able to open another card from the selected card, i.e. UI that can continue to be stacked. I then realised that Appy Weather would benefit from these changes too. For example, to be able to swipe between the hours in a day, days in a week etc. Or to open a specific hour from a day. A week later these changes have been copied across. Its extensibility is a win from a developer perspective, and it will benefit users too. The fit and finish is on point too thanks to the connected animations. So much so, I made a big call this week: cards when tapped on will automatically open in full screen.

That’s a change from the existing version whereby a tap expands the card with more details, but for it to go full screen required a long press. The previous intermediary state existed because my animation game was weak, and the unique data in the full screen designs wouldn’t justify the relative effort associated with a long press (every second counts, and a long press may not be much more than a tap in absolute terms but it does feel like it!). Neither will be the case anymore. The connected nature should make going full screen not feel any slower than a tap to moderately expand, and you’ll just want to go full screen because the data and its presentation is considered thoughtfully (for example, the Now card in fullscreen will show differently to Next Hour’s because the time should change requirements). Long presses are not necessarily expected and more likely to be missed. And so, a tap should prioritise what I think will be more useful to the user.

That’s not to say there won’t be a long press associated with cards but if there will be, it’s more likely linked to modification of state than presentation of data. Predictability is always a usability win. In the current version, some cards expand on a tap, others go full screen actually, and some don’t do anything. Although each has a visual cue (or none) to suggest behaviour, I would much prefer if there were none needed because they all behaved the same (this means every element within the existing Timeline will have a full-screen version, which has been a lot of fun to design). The only thing I haven’t nailed and may be a catch is making it feel just as quick to move on to the next point of interest. Previously (currently) you could just scroll, but at the moment you’ll need to close the full screen card first. This needs to be 👌 too. To be confirmed.

Have a great Sunday!

Best,
Bardi

Working on multiple projects at a time can be tough because progress on each is theoretically reduced by at least half. But what’s arguably even worse is regularly switching projects after a lengthy break. The time it takes to re-adjust is an unnecessary waste. I’m a strong advocate that the start of any point in time, whether it’s a week or year, is the best time to make a change. At least that’s what my brain optimally responds to. That said, I consider the preceding period ideal to prepare optimisations for so that when the day comes, your training is complete. That is, I don’t want to press a hard reset button on January 1, but to soft launch during the next couple of months to make sure 2022 is my most prolific. I know for there to be multiple releases, I’ll need to dedicate similar attention to both, and nail my timing.

I finished the week on the second unannounced project, after taking a break from it for a month. It was a painful initial restart, but once I got over it, it was a net positive. A lot of UI building blocks originally built for Appy Weather were generalised to be app-agnostic. These are foundation pieces that will significantly reduce boilerplate code for future projects. More relevant were architectural differences between the two that made me question the approach I had taken with Appy Weather. It was a more simple take. And unless there’s a strong argument for rejecting simplicity, it’s usually the best option. So that’s a change I intend to make next week.

When you work on something, you’ll make mistakes. And those mistakes are the learnings for the next thing you work on. But when you work on more than a thing, it benefits from your learnings in real time. And, actually, even if the second project doesn’t offer any valuable insights that are directly applicable to the first, any time away from its grind mean you come back to it with fresh eyes. You questions things that you wouldn’t have seen if you were at it constantly. I know over the last year I’ve routinely weighed the pros and cons of spreading my focus. But approaching a new year, it’s become clear that I must make it work because it scales my possibilities. I’m reaching a level of technical competency whereby a generalist mindset could actually be my weapon of choice. That is, solve any problem in a way that I – not the app it’s originally for – benefit from it the most.

Have a great Sunday!

Best,
Bardi

I put out what may be Appy Weather 1.0’s last update on Android this week. This doesn’t mean 2.0 is imminent, but just that I don’t have enough justification to put out any more updates for it. The primary reason being I consider the version in a sense complete – from a functionality as well as reliability perspective – and so any improvements can be deferred to 2.0. Therefore any time I spend on the current version unnecessarily delays the next. The other reason is from November 1 any updates to the Play Store require apps to be using a version of their billing library that I’m not on at the moment. When these requirements were first announced more than a year ago, I didn’t do anything in advance because I anticipated 2.0 to be out before then :( This might be a simple change, or it might end up being a pain. It touches such a critical area in the experience – and my livelihood – that I would much rather continue depending on the deprecated APIs that just work. So, I made sure the last update fixed any bugs that I considered worthwhile, enabling me to proceed guilt-free as I’ve not carelessly left any major inconvenience behind for any users. These plans would however change if there’s a serious issue that surfaces at some point, more likely due to external factors like an Android system update. Hopefully not!

Have a great Sunday!

Best,
Bardi

According to some, intelligence isn’t what you know but awareness of what you don’t. Based on this definition, I’m getting more intelligent. Following up last week’s charting adventures, I wanted to challenge myself further: a chart that dynamically and continuously animates visualising the precipitation forecast. This was the last feature my external chart library boasted that I wanted to build my own version of, therefore enabling me to drop the dependency altogether. For a change, I decided the fastest (smartest?) way for me to accomplish this – and learn in the process – is by paying someone else to do it. I hopped onto Fiverr and posted a job request, setting a budget of $100 with expected delivery time of a single day (it was a big job for me, but for someone better than me, a day should be sufficient). It wasn’t long before I received a flurry of offers. Almost all clearly didn’t read the brief in their response and copy/pasted generic interest. Few were within budget but many above, some asking for as much as $800! Not impressed, I decided to directly reach out to an iOS developer on the service who was an established seller with ~50 positive reviews. They replied immediately and said they would give it a go. But despite their best efforts, they couldn’t meet the requirements – not even close – and we both agreed there’s no point for them to spend any more time on it. No money was exchanged.

I then reached out to an ex-colleague accomplished developer. I asked whether they 1) know how to accomplish what I’m after and 2) whether they’re available to do it themselves for whatever their hourly rate was. Although they had no direct experience, they were curious to learn, and see how much they can achieve in a short time. Free of charge! Although they didn’t fully deliver on the requirements, they set me on my way. I took over and managed to get it to look like below:

It still requires a lot more refining but that’s a pretty solid turnaround for a few hours. And with this, I have 100% control/knowledge on the chart drawing code. This is going to make a big difference in getting them to feel how I want and present what I need.

The unproductive experience on Fiverr was important. With most of Appy Weather 2’s logic in place, I’m starting to think of the Android rewrite. I could do it myself but this would mean my 2022 will be mostly spent on this, as I’m learning a whole new language and UI framework – this is the appeal of cross-platform frameworks that I’m rejecting this time around. Or I could hire someone to do the job. Definitely not from Fiverr though. I did some research and came across Proxify. They interview/vet coders so people like myself can feel assured that you’re hiring someone competent. But it comes at a premium: ~£30/hr. My requirements can be broken down into two parts: 1) translate the logic from Swift to Kotlin and 2) build the UIs. It’s likely I’ll outsource 1) whereas 2) is a possibility too. But this could end up costing something like £10k! Perhaps less, but possibly even more. The question is whether I feel the 2.0 on Android will result in increased revenues that would at least make my money back over 6-12 months. I feel it could, but I’m not 100% yet. In the meantime, I’ll probably start conversations with one or more agencies soon.

Have a great Sunday!

Best,
Bardi

This week was spent mostly working on charts. The current version of Appy Weather has quite a few, but v2 makes them an integral part of the experience. Prior to this week, Daniel Gindi’s popular iOS charts library was being used to create them. It provided a ton of functionality and customisation. That’s arguably because it’s built on a legacy UI framework (not SwiftUI). So there was something about its look and feel that didn’t feel modern, and therefore misaligned with the rest of the app’s UX. I had similar feelings when actually working on it. The codebase was massive and just identifying the relevant area of code was a challenge. Forget about the hacks involved to make the desired tweaks. So on Friday I decided to see whether I can build something myself. 30 minutes later I had. What! It was a range bar chart, similar to the one already being used on the Daily screen visualising the weather for the next seven days. I then challenged myself to go one better. Am I able to have another visual within it to indicate precipitation levels? Yes I was. To round it off, now that everything was in SwiftUI, could I get it to animate? Of course! A lot of the credit goes to SwiftUI (and its incredibly community). I have never felt so empowered when building interfaces. I would never have even considered attempting this in any other UI framework, forget about actually pulling it off. I need to take some credit too.

Earlier in the week instead of directly focusing on the chart’s visuals, I went on a side-quest to optimise the data it receives as inputs to make it seamless to display any data in chart form. See, most data points have different units and scales, e.g. the UV index ranges from 1 to 11, and that’s different to temperature. For charts to display either correctly, either I customise chart’s interpretation of the data on a per point basis (what I do currently in v1), or I somehow make the values it receives to follow a consistent scale. It took a bit of trial and error and some creativity but I cracked it. What this facilitates is super easy charts to build and maintain, and therefore expect to see a lot more of them in v2. It’s going to be a visual treat.

Have a great Sunday!

Best,
Bardi

Have a great Sunday!

Best,
Bardi

What is good weather? What is bad weather? These are difficult questions to answer, and arguably impossible to generalise. It varies per person with location a big factor. I remember getting a confused/unimpressed email from a user querying why I show a sad face when the weekend is expected to rain. He was clearly not a Londoner. But likely someone living somewhere where the occurrence of rain is considered special, or maybe someone who benefits from it somehow (I can confirm farmers use weather apps). So, on one hand, I’ve sort of given up on the idea that the app would make these generalisations. But I want to delegate this responsibility to the user. Let them inform the app what they consider to be ideal conditions and whether they’re bothered by the rain.

The other semi-related goal is to make it easy for users to understand what the weather will actually be like in x-hours by routinely contextualising it on their terms. Because a number is meaningless without context. Version 1 already indicates what the temperature difference between today v tomorrow will be on the Timeline for this reason. Did you think it was cold today? Well, it’s even colder tomorrow. The temperature as a standalone number matters less than what you feel. This clarity occurred late last night when I was sketching. And this didn't happen by accident. With the backbone of v2 pretty much there, I can ideate once again. This usually occurs at the very start of a project when it’s the formation of these ideas that motivate you to get started. Then it goes on hiatus until you’ve returned from dev slug – an unforgiving place that some never return from. I just about managed. I’m pumped for the next 12 weeks. The fun restarts.

Have a great Sunday!

Best,
Bardi

I love you, my love.

Best,
Daddy

I’m aiming to create tactile experiences with the next generation of Third Culture Apps. To achieve this goal, the apps need to animate naturally at any interaction point. This week’s R&D was spent on whether I can get a card to expand to fullscreen. I had actually already achieved the intended effect several months ago, but with work progressing, it became apparent that it was more of a hack with undesired side-effects. I have two options at this point: either keep trying to figure a way – it’s surprisingly not a popular request and may actually not be possible due to the UI framework’s relative immaturity – or give up and just navigate to a second screen, i.e. the experience becomes less fluid and technically disconnected. As always, my requirements are quite specific which make Googling a solution a challenge (ones I’ve found require the card in its collapsed state to be of a fixed height, whereas I need their height to be variable). I’ve found in these circumstances I’m more productive when I’m actually not behind the keyboard trying to force an outcome. I’ve belatedly realised – and come to appreciate – that coding actually benefits greatly from creativity. Any problem does.

Have a great Sunday!

Best,
Bardi

Friday was my first full day of uninterrupted work. And boy, did it feel good. Everything is relative though, right? I remember having these same hours to work before and it never feeling adequate. But considering everything that happened in the last five months – second baby followed by the school summer holidays – six hours feels like a substantial time. There are a few reasons why I think I feel this now. When you feel like you’re playing catch up, slacking off is not an option. I’m a better software architect as well as more comfortable with Swift. A lot of the nitty gritty work is complete. In other words, I’m coming back into the game with better skills on solid foundations to build on top of and just grateful to have any meaningful time to focus, i.e. I can get a lot more done in six hours today than six months ago. And so when it’s school pick-up time, it’s a stop I’m pleased about.

Thanks to these developments, my evenings have more purpose and structure too. I finally watched my first WWDC 2021 video that had been queued for months – 40 minutes that will make a big difference next week in terms of UI optimisations. On the back of a week when I finally – pretty much – wrapped up the code generating summaries for a period of days. What’s left is doing similar for minutes that’s used when precipitation is forecast over the next 60 minutes and when I have access to minutely data. Also – and finally – generating summaries for days based on hourly data (attentive subs will recall I had completed hourly summaries for an undefined set of hours already, but those strings won’t be optimal for when the hours represent a full day). This is since I don’t want to depend on weather service providers’ because they can be unhelpful – poor even, if not in English then other languages – and I want the summaries to feel consistent.

Have a great Sunday!

Best,
Bardi

My boy goes back to school tomorrow. The summer holidays are up. I didn’t work as much as I needed to over the past six weeks. But not any more than I wanted to. It took to my 30s to realise – probably after having a kid – that life is simple. It’s always a matter of priorities. What is the more important thing at any moment. If I wanted to get more done over the holidays, I could have walked to the nearest coffee shop and code in peace. I love what I do. It’s not work. It’s a passion. But there’s nothing I’m more passionate about than being with family. The path I’ve taken with independent development enables me to maximise this time. What is the point of an iOS release if it’s at the expense of my presence. Not enough.

Fortunately, I’m still profiting from the business strategy set when I launched Appy Weather on Android two years ago. Specifically going with subscriptions without a lifetime purchase option. This combined with last year’s relentless pursuit to appeal to Dark Sky users who were looking for a new weather home has meant I could afford to get away with a summer that has little to show for in terms of progress. August 2020 was my blockbuster month when Dark Sky became unavailable. Although I knew I won’t make as much this time around because subscription retention is a difficult business – despite now taking 85% of each sale – I made more than I was expecting. Somewhere around 70% of last year’s figure. Not bad for an app that’s been in effectively maintenance mode for the last 12 months.

And with school reopening and darkness beckoning, there are four months to go – and 16 more newsletter episodes – for me to re-prioritise to get through as much as possible before the year is up. A year that began with me outlining eight projects I aimed to ship within the next 12 months. Even if I bring my A-game to the time remaining, it’s still unlikely I’ll end the year with anything other than the book to show for it. But the goal at this point is to start 2022 really strong. These next few months will be critical.

Have a great Sunday!

Best,
Bardi

I went four days without the laptop this week. Some record. Back now but not feeling any more motivated than I was before the break unfortunately. I did have an entire Friday all to myself afterwards though. The first time for a year. The last time I was home alone, I made the big call to go all-in on native iOS development. The outcome this time around was less profound. Good progress was made for what was effectively an 8-hour shift. It did make me wonder how much further along I would be on all projects if I consistently had this much time every day to focus on work. That said, I’m confident once the rewrites are complete, I wouldn’t need this much time anyway. In fact, the rewrites are primarily motivated by the idea that they’ll significantly accelerate development. Achieve much more in much less. For next week, possibly the biggest item is to test Appy Weather and ruff on Android 12. It’s probably being released in a couple of weeks, so need to make sure there are no issues with either. I’m slightly concerned 12’s visual design changes – particularly with widgets – may have some unintended side-effects that need to be attacked asap. I should have looked into this sooner, but there’s been absolutely no motivation for some time to work on existing projects (for a v1, they’re feature complete and with no serious issues either I’ve been comfortable with putting their development on hiatus until their v2s ship). Besides compatibility tests, I’ll possibly use it as an opportunity to fix a few niggles that have been reported with both over the last few months. And perhaps slip in the book release.

Have a great Sunday!

Best,
Bardi