wyDay blog

Firstly, I wish everyone safety and good health during this international health crisis. Stay home if you can.

The coming economic recession or depression

In the United States (where this company and all of its workers are based), the bungled non-response from the Trump administration to this biological threat will, at the very least, bring on an economic recession. And, depending on the details of an economic bailout (size, structure, etc.), might also cause an economic depression.

There might have been an economic recession even with an intelligent, considerate President that took advice from experts seriously. But because we currently have a lying ignoramus as President the world is reaping the "benefits" of that choice.

Economic considerations are, and should be, secondary to the health and survival of every single human on this planet.

But because we're a service that companies depend on, we need to talk realistically about our company during an "economic downturn". Or, to put it bluntly, I need to be callous and talk about money when people's lives are still at risk.

wyDay is prepared to weather bad economies

Our company was formed and started selling products before the "Great Recession of 2008". We started with very low overhead and grew during a period of time that a lot of businesses were shrinking or going out of existence.

Surviving and growing during bad economic times is in our DNA. We have no debt. We have no VC funding. We have very low overhead. We've always had a 100% remote workforce. And we have cash reserves large enough to continue to grow during an economic collapse — an economic collapse that has already begun. During "good times" these choices slowed our growth. During bad times these choices ensure our survival.

Once the dust settles, and it becomes clearer just how bad the economy will get, we'll resume hiring.

In the meantime, we'll continue to develop and release our products at the same pace and quality has before (deliberate pace, high quality).

I wish everyone safety and health.

- Wyatt O'Day
Founder & CEO of wyDay

Today we've released TurboFloat 4.3. The marquee feature of this release is that when your app uses the TurboFloat library your app can now release any active leases when a computer goes to sleep. And your app will also attempt to regain that lease when the computer "wakes up".

An example of a computer going to sleep is when your customer shuts their laptop:

The laptop is now asleep. If you were using TurboFloat in your app, and your app had a lease before the computer went to sleep, the lease would be dropped immediately. This frees up the lease to be used by any of that person's colleagues.

Humans are messy and unpredictable

This feature is just the latest example of our focus on real-world user-behavior. A customer isn't going to switch to every app they have open, see if it's using floating licensing, and if so, invoke whatever method you've created to drop the lease while keeping the app running.

That would be a nightmare; no one has time for that.

A real person is either going to just walk away from the computer (and the computer will put itself to sleep after a few minutes). Or the person will explicitly put the computer to sleep (for example by shutting the laptop).

Our job is handling this, and other real-world behavior, so you don't have to.

If you're not already using TurboFloat for your floating licensing, signup for LimeLM today (it's free to try — no credit card needed).

We're proud to announce that we've made it possible to sell your app on a per-process-instance basis. Meaning you can directly limit how many instances of your app your customers can run at any one time.

It's available now for all LimeLM customers!

This new per-instance lease issuance is the alternative to the per-user-session leases that TurboFloat Server issued by default. The differences between the two is shown in the gif above as well as described in "Fine-grained control: per-instance vs. per-user session leases":

With the release of TurboFloat 4.1 we added the ability to issue leases either on a per-process-instance basis or a per-user session basis. This gives you more control over how you sell your software and how it's used by your customers.

For per-user-session leases, one lease is issued per-user session on a machine (real or virtual) that is using at least one instance of your app. For example, "Sally Doe" starting your app on a shared server will be able to start multiple instances of your app and it will use that one lease regardless of how many instances they start in that user-session on that machine.

For per-process-instance leases, one lease is issued for every instance of your app started. Every separate process-instance of your app started will request a license lease whether the separate instances are in the same user-session or are in multiple different user-sessions.

So, how do you use it? Simple: first, make sure you're using the latest version of the TurboFloat Server and TurboFloat library (get them on your API page). Then create a new TurboFloat Server key (or edit an existing one) and select the "per-process-instance leases" option.

That's it. We handle the rest. Easy-peasy, lemon (lime?) squeezy.