New option: AutoFire

[kevinweber]

Automatically trigger the popup after a certain time period.

[carlsednaoui]

@kevinweber Thanks for the PR but I don't think I'll be merging this. In essence, this PR defeats the purpose of ouibounce which it to fire an event when a user plans on leaving the site.

[kevinweber]

I think that this feature is interesting for many users of exit-intent software. The feature actually doesn't wipe out the use of exit popups.

1. The popup still fires when the user wants to close/switch tabs using his cursor.
2. But additionally, when it takes very long to close the tab or when the user switches tabs using his keyboard, the popup can appear.

Alternatively:
Do you want to implement something like an "on load" hook? It's similar to the callback function but it must be possible to call your script's functions even when the popup is not yet fired.

[carlsednaoui]

My dislike for "time-based events" is the reason I hacked up ouibounce — I believe these provide a less-than-ideal user experience (ouibounce being the less evil of all options out there).

I'm happy to leave this branch open since you already put the work into it but don't feel comfortable morphing the philosophy behind this project.

Re: the on-load hook: ouibounce should be loaded on pageload, because of this, I feel as though it isn't necessary.

Thanks again for spending the time on this @kevinweber I do really appreciate it. I hope you can see things from my perspective too 🍔

[kevinweber]

Yes, I see. Your philosophy is really cool and I appreciate it.

What do you think of extending the API? Like that:

  return {
    fire: fire,
    disable: disable,
    checkCookieValue: checkCookieValue,
    _fireAndCallback: _fireAndCallback,
  };

[neils1]

ᐧ
How about on mobile devices? A time based events for mobile sites would be
perfect, if it was time since last scroll * number of words on screen.

On Sun, Nov 2, 2014 at 8:30 AM, Kevin Weber [email protected]
wrote:

Yes, I see. Your philosophy is really cool and I appreciate it.

What do you think of extending the API? Like that:

return {
fire: fire,
disable: disable,
checkCookieValue: checkCookieValue,
_fireAndCallback: _fireAndCallback,
};

—
Reply to this email directly or view it on GitHub
#71 (comment).

[jescalan]

Yeah I've gotta side with @carlsednaoui here and say this isn't a feature I'd be comfortable including. But that's what open source is all about, you are welcome to fork it into your own version that does include this feature!

[carlsednaoui]

@neils1 ouibounce was not (and cannot) be designed for mobile devices since there's no such thing as "finger tracking" (yet :)

[carlsednaoui]

👍 +1 on what @Jenius said :)

[neils1]

The workaround I was thinking was susing jquery to make the whole page an active state and then calculating word count *average reading speed and then if someone doesn't scroll down after that time triggering a popup.

[jescalan]

@neils1 that method seems like it would generate a lot of false positives. I think one of the goals of ouibounce is to generate very few or no false positives. Popups are annoying, especially if they come up seemingly randomly. I would go no on that idea, although I must admit it is very creative!