On December 26
Xiao Ming asked me: “Wechat mini program recently released a new update, adding sharing, template messages and qr codes with parameters, should we jump on the bandwagon and do something?”
Before small program just inside measure, developer community already boil for it. I don’t think so, “but it is the improved version of the public number, not worthy of attention.”
Now the mini program has added sharing and messages, and can also publish qr codes with parameters. “It doesn’t seem so chicken anymore.”
“What about it?”
“Make an activity ticket small program!
“Generate a QR code with parameters for each event, which can be put on the poster or web page, scan directly to the event page, use wechat to pay for the ticket, then send the ticket number with template message, and share the event page with friends.”
“Wow, that’s the best scenario.”
We were so excited about the idea that we started right away.
How are you? My name is Pinky.
The first step is to choose a name and design an icon. The name we initially thought of was “small ticket,” but it’s taken up. Then simply a little smaller, called “small ticket.”
Design and Development
I’ve always hated high-fidelity prototypes because I felt they limited the flexibility of the product, so I just sketched them out on paper and worked out the details as I went along.
This time, we tried a different approach: create a high-fidelity design first and start development later. Because the cost of adjusting the design is much lower than adjusting the code, the finalized design eliminates the need to switch back and forth between development and design. The results were better than expected.
Here is a comparison of the design drawing and the final implementation:
Notification and sharing are also made easier by using the template messaging and sharing API provided by the authorities:
Two people worked on the design and development of the miniticket. I’m in charge of the design and front end, and Xiao Ming is in charge of the back end. From name selection to approval, the project took eight days to develop.
There are fewer than 10 pages in total, but it’s a complete system with users, activities, payments, orders, inventory, and more.
In the front end, considering that the API of the small program is still changing rapidly, the third party framework may not be updated in time, so we directly use the official framework. From the start of construction on December 27 to the approval on January 2, a total of 30 commit products were finally produced.
For the back-end part, we used LeanCloud as the back-end infrastructure for fast implementation, generating a total of 32 Commits.
So far the development work of small ticket son project came to an end, such as small procedures officially released.
A little program can go a long way
The development experience of small ticket projects is impressive. Ultra high development efficiency, so that the small program trial and error cost is lower, so bring rich possibilities, TSK TSK, a lot to be done.
Above is this interesting small program development experience, I hope to give you some inspiration.
The picture above is the poster of the “Little Program, Big Action” event we are planning to hold in Shanghai. If you are free on January 15th, please come and join us.
Farewell!
Oh, and one last thing I almost forgot to mention:
Introduce Tiny Group
Tiny Group is a company that specializes in developing small programs. From applets to developer services, we’re going to do a lot more around applets.
Welcome to our website: tiny.group
Are you interested in applets, too? Add my wechat to chat:
