I have released a few versions of Eventail since my last post.
The notable major update 3.0 has brought the interactive mode. When active, the widget will give each entry more space in the day view and populate each entry with buttons which can launch various actions.
The actions can open the events or reminders in an app of the user’s choice, start navigation to a specific event, join a conference call and more. The full list is described in the documentation.
This new mode is malleable and makes it easy for me to add integrations with other applications in the future.
The 3.1 update for Eventail has brought support for, what I call, “universal URLs”. What this feature does is that any event or reminder that has the URL property set, will have a button in the widget to open it.
First usage that pops to mind is adding URLs to events manually, and there are some great candidates for that. For example you can use the iOS shortcuts URL scheme to launch a shortcut.
Another handy feature of iOS is that it will add a callback URL here every time you create an event from a message, be it an e-mail or iMessage. Since the message itself can contain useful information (such as a door access code for your hotel or flight reservation number) the ability to show it immediately from the lock screen is very practical.
In version 3.1.1 I have added a possibility to define custom URLs for opening events and reminders. This way, I will not have to manually enter all possible URLs. A simple template will do. I will try to scour the Internet and add as many URLs for popular apps into the documentation.
Sneak peek into the future
Next release will bring a possibility to display the reminders with due dates inside the Todo widget instead of the Calendar view. Possibly there will be some new integrations as well.
Your application is finished and uploaded to the App Store. You are happy and eager to see the reactions from customers. Then, a review like this lands in:
by disappointed person – Feb 16, 2019
Cuándo será en español, la compraré....
After a few dozens of such reviews, you may be tempted to translate the application into another language. In this article I will point out a few reasons why that might be a bad idea and give a few pointers for when you decide to pass the hurdle.
Translation may bring other people into the churn
Working alone on an app makes a things easy and agile—writing new features and fixing bugs takes little time and once they are written nothing stops you from releasing the new version.
If you translate the application into a language that you do not master yourself, you need to bring in translators and to depend on them. This ties to someone else’s schedule every time you modify a visible text in the application.
Someone else might be on vacation, they might be sick or have other stuff to do and will not scramble to translate things for you. You have to plan the releases around their availabilities.
Translation brings additional (boring) work
I assume that you have thought about internationalisation from the beginning and that your code uses localisable strings everywhere. If it does not, this should be done before any translating can start.
You will have to translate all of the strings in the application and the whole UI. Be aware than many terms that are common in English are do not always have counterparts in other languages. This concerns a lot of technical and computer related vocabulary. This means that you will need to do due diligence to find out what terms are colloquially used in the target language for what you wish to describe.
Some languages handle the context differently from others: A menu with a lot of switches may only require a short label in front of each switch in English, but demand longer descriptions when translated. This may require alterations to the UI because the labels might no longer fit in the original space.
Once your application has been translated, you are halfway done. You also have to think about screenshots, documentation, marketing material1 and the website.
Translation is a commitment
Features which modify visible text will generate more work from now on. Screenshots, for example, are required for each supported language. Depending on your platform, their generation can be automated by tools such as fastlane2.
Be prepared to find yourself in a situation when you have finished the features, fixed the bugs, and are ready to submit, only to realise that you have forgot to translate the one button which you have added. If you are using translators, pray that they are not on vacation.
Expect to receive support mail in foreign languages. If you have used an external translator, you may not be able to answer them.
A few hints for future polyglots
If you have considered the above and are ready to start translating I can give you a few hints:
Minimise text in your application
Put as few labels as possible into your applications. Consider them like you consider code, if it exists it must be maintained.
I have removed some settings from my app at the last minute, so I would not have to translate the associated controls. If a feature is hard to explain in a foreign language, it might be too complex to use as well.
If a label can be replaced by a pictogram do so. A good example would be to use a slider with small and large character at either side rather than listing text sizes.3
Use textual representation for your translated strings
In iOS, you can use full Storyboards or string lists for translating the UI. Stick with the plain text lists as they are easy to diff and mistakes in them are quick to spot.
Localisation will live next to the code in your SCM repository and it is important that its format be adapted.
Make the non-translated strings pop
Use a gibberish placeholder for untranslated strings and add them immediately after you create each new string. Most frameworks will use the default (usually English) label for non translated strings and this can lead to forgotten translations.
Translating an application might seem to be a good way to increase the number of possible clients and profit. But consider what you are giving up: having an application developed by a single person in a single language gives you incredible flexibility. This agility might be worth more than a satisfying few angry customers.
Increasing amount of tools are written for web, many presenting themselves as replacement for standard desktop applications.
For simple stuff this is fine, few people would like to install an application for every shop or transport provider.
Complex programs running in tabs hit an insurmountable hurdle: “they cannot implement correct keyboard shortcuts”. And it is a problem that nobody has figured out yet, it is a fundamental issue that will never be fixed.
Some examples that come to mind:
How would you open a tab in your web app? ⌘T opens a new browser tab. What about a new window⌘N?
How do you undo? In Safari ⌘Z undoes closing of a tab.
If your application provides a save option, what would you use? ⌘S will try to save a useless HTML document.
Another problem is selection. ⌘A selects everything, this is never what you want to do in an application, but it can be something you want to do on a webpage. This means you need to break one behavior or the other.
Although their cameras are superior on technical level1, people prefer pictures from other cameras because of increased brightness and saturation.
Of course there is nothing that stops iPhone and Pixel to do the same thing at the cost of losing information rendering further post-processing inflexible. That being said, I can imagine that being beaten by a Blackberry in a photography test must hurt.
The solution is simple. I am sure that if pictures after auto-enhance have been thrown in the competition, the results would be different. The winner might stay the same, but I doubt that iPhones and Pixels would remain dead last.
What Apple and Google should do is to add an option to turn on auto-enhance by default. This way no information would be lost and people who prefer pictures without it could disable it. It would make the pictures coming straight off-camera punchier.
But first Apple would need to fix their auto-enhance algorithm which makes everything orange.
Noise, dynamic range and colour reproduction are comical on some of the tested phones.
As a side project I am launching my YouTube channel Binary Campfire. I haven’t decided its ultimate purpose; but as others before me, I will start posting some videos about video games. Old ones, as that is what I play these days.
The first video will take us back to 1992, with a side scroller/shooter game Alcatraz.
The event held on the 30th of October solidified the idea roaming the Internet since a few years: ARM Macs are coming, and they are coming soon. A-series chips have caught up to all but the best Intel mobile chips1, so why is there an Intel processor inside the new MacBook Air?
I have a theory: A-series chips are not powerful enough–but in an unapparent way.
In my previous article I have predicted that Apple would:
Rename the current MacBook to MacBook Air.
Discontinue the 13″ MacBook Pro without TouchBar.
Introduce a new, cheaper, 13″ computer called MacBook.
This did not happen as predicted. What was announced is a new MacBook Air, which is a 13” version of the current MacBook. Other laptops in the MacBook line were untouched.
What I think will happen next year is:
Apple will introduce a new 12” MacBook Air and “discontinue”2 the MacBook line.
Apple will introduce a new 13” MacBook with Apple ARM chip3.
But herein lies the problem. Which chip would go in? If Apple took the A12X processor from the current iPad Pro and added a bit of RAM, this setup would breathe at the neck of the current 15” MacBook Pro with Touchbar4. This would have serious implications for the Pro line as the only differentiator would be the software they can use.
In order to offer compelling Pro hardware, Apple needs to make a beefier A-series chip. One that would give even the Intel desktop chips a run for their money.
A new episode of Dos Game Club podcast was released today. This
22nd instalment is about a legendary game: The Secret of Monkey
I have been fortunate to be able to join Martijn, Florian, Mike, Philipp and
Esko to discuss this great game during an epic 3 hour session. If you enjoy
retro gaming and especially DOS games, give this podcast a try!
Every month we select a different game to play and discuss on the forums and
IRC. Martijn and Florian then invite a few guests do discuss the episode and
record a podcast session.