Lynky Launches in Open Beta
677 commits, and 14K lines of code later, Lynky goes open beta
When I started designing and coding the Lynky platform, it was out of necessity for an extremely flexible URL builder solving multiple problems and not focusing only on one as most of the currently available solutions on the market. That level of flexibility would simplify the workflow and bring great benefits to any business, creator, and any other person on the internet. So right from the start, it started with a clear vision of what it would be and how it should work.
That vision was underestimated in how difficult it would be to get a project of that size of the ground. The deadlines were constantly pushed further, always for different reasons, but mainly for engineering challenges. The initial goal was to offer a set of tools that would set the foundation for further developments, which seemed like an easy task at the beginning but building a solid foundation requires the right choices and design decisions, which often made me to take a step back and rethink some parts of the platform.
After months of work, and although some of the key features were still in development, on October 7, 2021, Lynky was launched in private beta for internal testing and bug hunting before going any further. This was a pivotal moment in understanding what was wrong and how some things should work. During that period I made some significant structural changes and kept improving things, which at some point, it seemed like it would stay in private beta forever, that there was no ending no writing code. But, 677 commits, and 14K lines of code later, Lynky finally goes in open beta.
So what does open beta even mean? Open beta means that Lynky is fully functional, tested, and operational for wider usage, but some parts are still under testing and small changes could still happen without drastically affecting your workflow. Anyone can signup and start creating and sharing content.
There are many cool new features in the pipeline, but at this moment the goal is to fix some small things, stress-test, and enforce the current structure. After which it will be a stable release, and we’ll go full steam ahead.