Question 1

How to use Ecno to show a tutorial only once per app install?

Accepted Answer

Initialize Ecno at app launch, then check if the tutorial task has been done in the .appInstall scope using beenDone, and mark it done after showing. The README provides code snippets for similar use cases.

Question 2

Ecno vs Core Data for managing user task states in iOS?

Accepted Answer

Ecno is simpler and lighter for basic task tracking using UserDefaults, ideal for one-time actions like tutorials. Core Data is better for complex, relational data with more features but higher setup overhead and learning curve.

Question 3

How to attach extra information to a to-do task in Ecno?

Accepted Answer

Use the toDo function with the info parameter to pass a dictionary, which can later be retrieved with infoForToDo for context, as demonstrated in the usage examples for banners.

Question 4

Can Ecno handle tasks that expire after a certain time?

Accepted Answer

Yes, by using the .until(TimeInterval) scope when marking a task as to-do, it will only be valid until the specified time from now, useful for time-limited actions like banners.

Question 5

Is Ecno suitable for tracking in-app purchase tutorials across app updates?

Accepted Answer

Yes, with the .appVersion scope, you can manage tasks per version, ensuring tutorials show only after updates if needed, leveraging the built-in scope flexibility.

Question 6

How to check if a task has been done more than 3 times in a session with Ecno?

Accepted Answer

Use the beenDone function with the numberOfTimes parameter set to .moreThan(3) and the scope to .appSession or custom intervals, as shown in the conditional checks example.

Ecno

What is Ecno?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions