🚀 Help Shape the Future of KTL - Send Us Your Usage Data!

API & Custom Code Show & Tell
1

Hey everyone,

I wanted to share some exciting news. Last week I had a very productive discussion with the Knack team about converting KTL to next gen - what we’re calling KTLNG. We’re making real progress on the path forward, and I’m genuinely excited about what’s coming.

One of the key things we agreed on is that we need to understand which KTL features matter most to you. With over 180 keywords and options available, we want to make sure the transition to next gen prioritizes the features that the community actually relies on day-to-day.

And this is where you come in.

How You Can Help (It Takes 30 Seconds)

I’ve built a simple, one-click way to share your app’s KTL usage statistics. Here’s how:

  1. Make sure your account has the Developer role

  2. Open the KTL Developer Tools popup - click on the version info bar at the top of your app (if visible), or press Alt+X (Option+X on Mac)

  3. Click the “Send KTL Usage” button

  4. Confirm, and you’re done!

That’s it. Your data is sent securely to my server where I can compile statistics about which features are most used across the community.

Note: This requires KTL version 0.35.1 or higher. While you’re at it, I strongly recommend keeping your KTL version up to date regularly. I only keep the last 10 versions on my AWS server, so older files will eventually be removed.

What Gets Sent? What Stays Private?

You’ll notice a question mark icon next to the “Send KTL Usage” button. Click it and it will open the KTL Discovery Hub in a new tab, where you can see exactly what information is collected and what remains private.

In short:

  • Sent: Which KTL keywords and options your app uses, your KTL version, your email and app URL. These are kept private - I will never send any emails, unless there’s a security emergency*.

  • NOT sent: Your application data, business content, database schemas, or anything sensitive.

Your privacy is respected - this is purely about understanding which KTL features are in use.

*It has happened on a few occasions that I discovered exposed API keys, leaving apps vulnerable to data theft, corruption, or ransomware - without the owner even knowing. Having a way to reach you in those situations can save your app. Every person I contacted was very grateful, and happy with the API-keyless solution I provided.

The KTL Discovery Hub

Speaking of which, I’d love for you to check out the KTL Discovery Hub:

This is a growing resource that brings together:

  • Feature catalog - Browse all KTL features with usage statistics

  • Documentation links - Direct access to docs, demos, and video tutorials for each feature

  • Community insights - See which features are most popular and discover ones you might not know about

  • Usage trends - Real-world adoption data from the community

Think of it as a one-stop shop for everything KTL - documentation, demos, videos, and now community-powered usage data.

KTL by the Numbers

I’m very proud to share that, according to Knack’s own data (as of January 2025), KTL is used by 242 accounts across 506 apps. Based on current AWS metrics, KTL gets about 40,000 hits per day. Each hit represents someone either opening a Knack app that uses KTL or refreshing an open page. That’s a lot of people relying on this library every single day, and it’s a testament to what this community has built together.

Why This Matters

The data you share will directly influence how we approach KTLNG. Features with high adoption will be prioritized. Features that are underused but powerful can be highlighted for better documentation. And features that nobody uses can be reconsidered.

This is a community effort. KTL has grown into something much bigger than what one person can fully steer alone, and your input makes it better for everyone. The more apps that contribute their usage data, the clearer the picture becomes, and the better decisions we can make together.

So if you have a few seconds, please send your KTL usage. Every single submission helps build a clearer picture, and the clearer the picture, the better KTLNG will be for all of us.

One More Thing - Quick Survey

I’d also appreciate if you could take a moment to fill out the Cortex R&D and KTL Survey. It’s short, and your feedback will help me better understand how you use KTL and where to focus efforts going forward.

KTL has always been a community-driven project, and this next chapter is no different. Let’s shape it together.

Norm

1 Like