a.k.a. why we wrote the Wultra Passphrase Meter library.

There is still a lot of misinformation about how the perfect secure password should look like. We were told a hundred times by “smart” password fields that we should choose a stronger password. For example:pendulum” is weak, but “P3ndulum!” is strong. Right? Wrong! This common misconception of “the password is good when there are enough characters from different character sets” is almost burned into our minds and it’s tough to explain it to a regular user why he/she shouldn't use such password.

With this in mind, most users tend to distrust a simple PIN code for anything related to online security. And with such mindset, users often ignore the fact that PIN itself can be strong or weak, even if it’s just 4 digits. …


As easy and trivial as it seems, processing money — especially the amount part — in Swift can be a huge pain in the ass.

Imagine we’re given this simple task in Swift for your Money-Exchange-Rate app we’re developing:
Deserialize transaction amount from JSON to Swift struct

Easy!

This should be 2 minutes to code. Let’s dive into Xcode and write our proof of concept.

Here comes the QA

Every QA engineer knows that input fields are the most common source of low-hanging-bugs that can be found in every app.

Let’s try to convert Euros to Bahraini Dinar he said.

Damn you, floating-point arithmetic!

Using floating-point type is maybe not the best solution here, try Decimal. Maybe it was a mistake to use Double in the first place anyway. …

About

Jan Koběrský

mobile developer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store