How I turned wedding website setup into a simple conversation and what I learned while building the experience.
The #OneAppPerQuarter series continues.
At the beginning of the year, I challenged myself to build and publish one application every quarter. That does not necessarily mean starting from zero every time. It means giving myself a framework in which I can experiment, learn, and turn ideas into real products.
For Q1, I built Lexter, an application that uses AI to extract information from documents and simplify the process of completing the forms required to register a company in Romania.
At the beginning of Q2, I decided to take a slightly different direction. Instead of creating another application from scratch, I chose to bring two existing products back to life and make them better.
The first step was adding an AI chat to my personal portfolio, lolotech.io. Instead of navigating through every page, visitors can ask questions about my professional experience, projects, and the technologies I work with.
The second step, and the main project for Q2, was Weddnesday.
From an empty template to a conversation
Weddnesday is a wedding website builder. Couples can choose a template, add information about their celebration, and publish a website where guests can discover their story, view the schedule, and respond through the built-in RSVP feature.
Until now, users personalized their websites by manually completing and editing each section.
The process worked, but I asked myself a simple question:
What if the user did not have to begin with a blank page?
That question led to the Weddnesday AI Wedding Assistant.
Instead of navigating through every field in the editor and deciding what to write in each section, users can have a simple conversation with the assistant. They share a few details about their wedding, their story, the venue, or the atmosphere they want, and the AI helps build the website around that information.
The assistant can generate and complete the hero content, love story, couple bios, event schedule, and RSVP labels. It can work in the user’s chosen language and continue refining the content through conversation. Everything can still be adjusted later in the visual editor. Not to remove control from the user.
The goal is to remove the difficult beginning.
AI as a natural part of the product
I did not want to add a chat just so I could say that Weddnesday has AI.
For me, the integration needed to solve a real problem. Writing all the content for a wedding website can become tiring, especially when couples must start from zero and find the right tone for every section.
With the assistant, the process begins with something much more natural: a conversation.
Users do not need to understand the internal structure of the template or know where every piece of information belongs. The assistant understands the website structure and places the content in the appropriate sections. This is how I like to use AI in software: not as decoration, but as a tool that reduces friction and makes a product easier to use.
The part the user does not see
On the surface, the result looks simple.
You open the chat, describe the wedding, answer a few questions, and watch the website begin to take shape.
Behind that experience, however, were many decisions, tests, and adjustments. I had to think about how to transform a conversation into structured information, how to preserve user control, and how to make generated content fit the existing templates.
I do not want to go too deeply into the technical details because, for me, the most important part is not the technology behind the feature.
The important part is what I learned while building it.
I used AI both during development and inside the final product. It helped me implement faster, explore alternatives, and focus on the overall experience. At the same time, my experience as a software engineer remained essential for architecture, product decisions, and validating the result.
AI accelerates the process. It does not replace the responsibility of building something clear, stable, and useful.
An older product can become exciting again
One of my favorite parts of Q2 was realizing that I did not need to start a new product to experience the joy of building something.
Sometimes an older idea does not need to be abandoned. It only needs a new context, a new feature, or a better perspective.
Weddnesday already had templates, an editor, and an RSVP system. By integrating the AI assistant, the product gained a new form of interaction: couples can describe what they want in natural language, and the website begins to take shape around them. This is one of the most interesting things AI brings to software engineering. It is not only the possibility of building faster. It is also the possibility of rethinking how people interact with applications.
Instead of learning the interface, users can describe the outcome they want.
What Q2 means to me
At first, I called the challenge #OneAppPerQuarter because I wanted to publish four applications in one year.
Along the way, I realized that the name can mean something broader.
It can mean one meaningful project every quarter. One idea taken further. One feature that changes a product. One experiment that pushes me to learn something new and ends up online, where real people can use it.
In Q2, I added two conversational experiences to my products: an AI chat in my personal portfolio and an AI assistant for setting up wedding websites.
They are not projects that will change the world. But they are real, functional, and available online.
And I am genuinely excited about the result.
I love the feeling of seeing an idea move from my mind into code and then into a product that someone can actually use. I enjoy it even more when the process helps me understand something new about AI, software engineering, and designing simpler experiences.
Q2 is now online.
The series continues, and ideas for the next quarter are already beginning to appear.
Learning is my superpower.