Automators 52: Charty with Rodrigo Araujo


Great episode! There’s something for about everybody - journaling, developers, data analytics, books, task management, Shortcuts wish list, health, podcasts, regular expressions and dragons!

I love Charty and @rodrigoaraujo really did an awesome job building it. One of the recent features I like is the ability to create your own themes that I made a shortcut for it. You can copy a pallete from Pastel for example and run this shortcut -

Speaking of scripting language for shortcuts, I have been using Just too bad that it’s still iOS 12 so you don’t have iOS specific features like parameters. Nevertheless, it’s still pretty solid.


Thanks for your kind words @supermamon!
Nice shortcut!
I took the liberty to update it to allow 3, 6 or 8 value hex codes, as Charty supports these three lengths :blush:

Did @RosemaryOrchard say she adds 100 tasks to OF and checks off 40 EVERY DAY!?!

1 Like

That was just the most recent day when we were recording :joy:
And that was a very busy day.

1 Like

I was thinking I don’t do/capture enough!

It really does vary. Bear in mind I’m moving house at the moment so have a whole host of extra stuff I’m dealing with :joy:

1 Like

I tested David’s query about if going to Run Shortcut action is slower then just running the actions in the original Shortcut.
So I made a Shortcut that has 10 “Run Shortcut” actions. Each one goes to the same Shortcut that has one “Wait 1 Second” action. At the end of the original Shortcut it shows an alert that the Shortcut has finished. Then I made A Shortcut that has 10 x “Wait 1 Second” actions and ends with the same Alert. Then I timed both Shortcuts. After doing about 10 rounds the Shortcut with the 10 “Run Shortcut” actions took on average 11.20 seconds where as the Shortcut that had no “Run Shortcut” actions ran about 10.80 seconds long. So about .40 seconds slower if you use 10 “Run Shortcut” actions as opposed to none. A very crude estimate would be that you add maybe around .05 seconds to your Shortcut for every “Run Shortcut” action you add in your Shortcut. I almost rarely use more than 3 Run Shortcut” actions in a Shortcut so I would say the time hit is almost negligible to the convenience of having sub routines in your Shortcuts.

Here are the Shortcuts if you want to test it yourself.

I always think the API boundary crossing penalty is relatively higher for the cases where what you’re invoking doesn’t do much before returning. And lower for heavyweight services.

So, for example, the overhead to invoke a 0.01 second service will relatively speaking be much higher than for a 10 second service.

But with the above numbers the architecture should be decided upon for reasons other than performance (and I say this as a performance person).

1 Like