Skip to content

Commit 3948abc

Browse files
authored
Add May 7, 2025 update
1 parent 4495221 commit 3948abc

1 file changed

Lines changed: 61 additions & 0 deletions

File tree

news-2025.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,64 @@
1+
## One Year Anniversary 🎊 (May 7, 2025)
2+
3+
We're approaching the one-year anniversary of the launch of Lightning Autofill v12 (May 15, 2024), when we decided to switch to the freemium model with the update to MV3. The LAF team would like to take a moment to look back on this journey. When we first started, we could barely cover our operating expenses after living off our savings while working on version 12. It got pretty hairy on more than one occasion, with lots of negativity early on -- a lot as a result of us shooting ourselves in the foot with critical bugs. There were bouts of second guessing ourselves. However, somehow we managed to overcome every challenge, push through every obstacle 💪. Fast-forward a year, and we're happy to announce that today Lightning Autofill on MV3 has reached a level of financial and code stability where we have some breathing room again.
4+
5+
Looking back, we have absolutely no regrets walking away from lucrative offers to buy Lightning Autofill that would have resulted in an uncertain future for our loyal users. Since we are now cash positive with the freemium model, we would like to officially announce our Halving Pledge as a way of giving back to the community as well as growing our subscriber base.
6+
7+
### ⭐ Halving Pledge ⭐
8+
9+
We pledge to cut our subscription prices in half every time our number of subscribers doubles. Starting with v14 (see release notes below), you will see a progress bar in Settings / Subscription:
10+
11+
<img width="355" alt="image" src="https://github.com/user-attachments/assets/b515002a-63fb-40e0-bf35-c60e33185fd1" />
12+
13+
In order to make Lightning Autofill more affordable for you guys faster, we will implement these milestone goals:
14+
15+
- When the progress bar hits **25%**, the subscription prices will be reduced to **$4.37/mo** for the Plus plan and **$8.74/mo** for the Pro plan.
16+
- When the progress bar hits **50%**, the subscription prices will be reduced to **$3.74/mo** for the Plus plan and **$7.49/mo** for the Pro plan.
17+
- When the progress bar hits **75%**, the subscription prices will be reduced to **$3.12/mo** for the Plus plan and **$6.24/mo** for the Pro plan.
18+
- When the progress bar hits **100%**, the subscription prices will be reduced to **$2.49/mo** for the Plus plan and **$4.99/mo** for the Pro plan.
19+
20+
The progress bar data is automatically retrieved from the Stripe API every hour. The starting subscriber count is the total number of subscribers at the end of May 1st, 2025. You can hover the mouse cursor over the progress bar to see the exact percentage at any given time.
21+
22+
### Lightning Autofill v14.0.0 BETA released
23+
24+
We've made a ton of changes under the hood, mostly migrating Firefox to MV3 and rearchitecting for the future. Here are the changes that you actually see:
25+
26+
- A new side panel for your profiles! This will also be the interface for upcoming macro recording feature, but for now you have quick access to execute and edit your profiles. You can toggle the side panel via the right-click context menu.
27+
- JavaScript rules now have access to global variables on the website, which makes them more powerful than ever. For example, if a site uses jQuery, your rules can also use jQuery.
28+
- Moved the "Parse labels" and "Profile expiration" options to the Operation section.
29+
- **[Breaking change]** The special built-in function `$()` was renamed to `LAF$()` to prevent conflicts with websites that also rely on the `$` global variable (e.g., jQuery). If you have JavaScript rules that use `$()` to reference something in the Variables tab, be sure to update these rules to use `LAF$()` instead.
30+
- A bunch of bug fixes to make for a smoother experience in everyday use.
31+
32+
**Changelog:**
33+
- Migrated Firefox version from MV2 to MV3
34+
- Added side panel for profiles and macro recording (WIP)
35+
- Allowed JavaScript rules access to website global variables
36+
- Changed $() to LAF$()
37+
- Improved JavaScript rules and variables processing
38+
- Moved "Parse labels" and "Profile expiration" to Operation
39+
- Replaced Autofill Stars with Halving Pledge
40+
- Fixed rare case where only first JavaScript rule executed
41+
- Fixed outdated info in Value column help bubble
42+
- Fixed local data potentially overwritten by empty Sheets
43+
- Fixed edge case where Advanced cloud data was corrupt
44+
- Fixed bi-directional sync corruption in some cases
45+
- Fixed JavaScript error after extension update event
46+
- Fixed JavaScript rules broken after re-enabling extension
47+
- Fixed rule generation bug after using Back button
48+
- Fixed popup notice showing when it's not supposed to
49+
- Fixed incorrect profile expiration in some locales
50+
- Fixed broken debug label in Firefox
51+
- Fixed context menu not updated after syncing from Sheets
52+
- Fixed incorrect badge count when executing profiles
53+
- Fixed issues invoking infobar on multiple tabs
54+
- Fixed UI glitches at high resolutions (pixel ratios)
55+
- Fixed JavaScript error when offline
56+
- Fixed errors when closing Google OAuth window (Edge, Firefox)
57+
58+
⬇️ **[Install](https://chromewebstore.google.com/detail/lightning-autofill-beta/oinjpibanhdbgelnjjjffimdlpcfpipa)**
59+
60+
---
61+
162
## Update on v14 (Apr 13, 2025)
263

364
We have officially started work on version 14! It will have some major changes, especially for Firefox users. Many users may not know that even though the Chrome/Edge version of Lightning Autofill has been on MV3 since v12, the Firefox version was still stuck on a clunky MV2/MV3 hybrid code base where we have legacy Firefox MV2 code living alongside MV3 code shared from the Chrome/Edge version, mainly because Mozilla's implementation of MV3 was too different from Google's implementation. As a consequence, this setup was prone to bugs and was a maintenance nightmare. Starting with [Firefox v136](https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/136), Mozilla's implementation of MV3 has been further aligned with Google's MV3 to the point where the Chrome/Edge and Firefox extensions can finally share the same MV3 code base, which will make maintenance a lot more streamlined.

0 commit comments

Comments
 (0)