Skip to main content

Wine Drop - breaking the ice

In this writing, I would like to share my experience of publishing my first game, and I hope it can motivate you to develop and publish games.

Brief introduction (feel free to skip it)


I have been passionate about video games and animation since I was five years old and I dreamt that one day I would publish a game so that people could play if they wanted to. However, it is not until I am almost done with my bachelor degree, I wrote my first game - a crappy one - but I am glad that I did the game. Then, I have joined game programming courses, hackathons, and game jams to learn to develop video games. However, all of the games were for "learning purposes", I have never thought of publishing any of the games because of being afraid of uncertainties (maybe it takes a lot of time to publish a game, is not a good enough game idea, does not have a good architecture, no scale, no way to earn money, just a learning project...). Then I realized that the excuses would be always there if you look for them. This time, I decided to make a game for publishing, so I built a team and made Wine Drop.



After publishing our first game Wine Drop, there are a few things I would like to share with all of you.

The feeling
I felt damn proud and accomplished when our team published our first game call Wine Drop. After pushing the first version of  Wine Drop to Play store, I wondered why didn't the games that I made so far didn't to aim for publishing from the very beginning. It was an absolutely great feeling which inspiring me on doing more games. If you are just starting the journey of games making just like me, I encourage quickly publish your first game and enjoy the experience.

Publishing a game is not necessarily tedious.
These are the steps are working well in this case:
1. Find some of your friends, relatives, colleagues, or classmates who like making games to work with to have more ideas, more fun. My preference is finding someone who has different skill sets than mine.
2. Choose free/affordable, simple, and familiar tools, in our case the tools are libgdxfirealpacaPyxel Edit, and Android.
3. Choose simple game on the internet to clone or to put a little bit more variant.
4. Make the simplest playable prototype and publish it.
5. Gather feedbacks and improve the game.

Following are the screenshots of the first version of wine drop. The total amount of hours put to this first prototype is ten hours of one person. We have 4 people working on this, so roughly 2.5 hours of working together.



Richer experience, much more fun and learning.
I have learnt a lot more after doing this "for publishing" game than those a lot more than the boring "learning purposes" ones. In this project, we learnt the whole process instead of just the coding game part. Moreover, The anxiety of someone is playing your game makes my team and I feel a lot more fun, challenged, and motivated.

Summary: Break the ice to see the sky. Have fun making games.

Meet the teams: Anh DuongNhat Nguyen QuangTuan Nhat NguyenAnh Dung Do

- ninjahoahong



Comments

Popular posts from this blog

My books review: "The retrospective handbook"

Overview: The retrospective handbook is a useful collection of tips for preparing and running retrospective for agile teams. The central point of facilitating a retrospective is the preparation. All the details - even the smallest details such as how much paper is available or what the colours of the using pens - play an important role in running a successful retrospective. In such preparation, the most important preparation is the relationship. It requires team members to have high trust with each other to address any problems in great details and find the most suitable solution for those problems. My impression: The tips for running remote retrospective would be really useful for anyone especially startups in my opinion. All the startups I have worked for so far have had some foreign teams either external or internal to save operating money. In addition, there are a lot of remote work to save office renting space and almost all of those startups followed the agile method.

Prepare Lubuntu 20.04 for software development

Prepare Lubuntu 20.04 for software development ninjahoahong After using windows , macosx , and serveral linux ditributions. For me, Lubuntu is the lightest and easiest to set up and run so far. If you search there will be two domains provide lubuntu which are lubuntu.me and lubuntu.net . You should use lubuntu.me which provide the most updated version of lubuntu . In this blog, I will focus on the additional packages after installation. Create Lubuntu 20.04 bootable usb Download Lubuntu 20.04 iso file. Create bootable usb using balena etcher or unetbootin . Boot to the usb and install Lubuntu . This is a starting screen using lxqt . Additional packages There are packages for apt and snap . I prefer apt since the app installed by snap command will take long time in the first launch. Web browser: brave I usually inst

The first taste of Rust - A simple you tube downloader

Recently, I just learnt Rust and using it to write a simple youtube downloader with reference from node-ytdl . In this blog, I would like to share the code and how did I make it. You can find the full source code here . Install development environment I am using Windows 10 and scoop package manager. Therefore, I use the following commands. Run scoop install rustup-msvc to install rustup . Run setx "%path%;%USERPROFILE%\\scoop\\persist\\rustup\\.cargo\\bin" to add rustup to the path. Restart termial (git-bash in my case) and check the installation with rustup --version; rustc --version; cargo --version Export custom RUST_HOME : export RUSTUP_HOME=$HOME/scoop/persist/rustup/.cargo/bin/rustup Install a toolchain for rustup : rustup toolchain install stable-x86_64-pc-windows-msvc Setup project Run cargo new simple_rust_youtube_downloader --bin && cd simple_rust_youtube_downloader to create and navigate to the project. Add these dependencies to