DEV Community: Akio Yamazaki

I made a Firebase Analytics plugin for iOS with Godot.

Akio Yamazaki — Thu, 10 Feb 2022 10:17:12 +0000

Overview

Recently I've been making games with Godot. Mainly for iOS and Android apps.
So, I want to add Firebase Analytics to Android and iOS apps respectively, Android is easy, don't need to change program, just Add repository url to build.gradle and Add google-services.json to the project(It's the same process as normal app development).
However, the iOS version is a bit more complicated because I need to write the program. I looked around for a good plugin, and found that there is no standard plugin that uses this, so I decided to make my own.
Here it is
https://github.com/funseek/godot-ios-firebase-analytics

How to create a plugin

This is described in the official page, so I used this as a reference.
https://docs.godotengine.org/en/stable/tutorials/platform/ios/ios_plugin.html

Usage

git clone

Clone the repository, including the repository for godot itself in the submodule.

git clone --recurse-submodules git@github.com:funseek/godot-ios-firebase-analytics.git
```



### Create a header file for the godot source



``` sh
./scripts/generate_headers.sh
```


The header file itself is created quickly, so you don't have to wait for it to finish.

### pod install
You can get the Firebase-related files from [CocoaPods](https://cocoapods.org/).

pod install




### Create the .a library file.


``` .
./scripts/release_static_library.sh 3.4

If you want to specify a different version, you can use the 3.4 version in the SConstruct file. If you want to specify a different version, replace 3.4 in the SConstruct file.

Copy to project

Copy the created .a file to your godot project.

cp bin/release/firebase-analytics/firebase-analytics.*.a $GODOT_HOME/ios/plugins/firebase-analytics/bin/
cp firebase-analytics.gdip $GODOT_HOME/ios/plugins/
```



### Export for iOS
Don't forget to check the Firebase-Analytics box in Plugins.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gnqu61b1mthnmxiodr2q.png)


### Xcode configuration
Use CocoaPods for Xcode, and add the following to your podfile.

pod 'Firebase/Analytics'.
pod 'Firebase/Auth'
pod 'Firebase/Firestore'



The steps to use CocoaPods are as follows.
1. run pod init (if you are not already using it)
2. add the above to your Podfile
3. run pod install
4. open the project .xcworkspace in Xcode
5. Copy GoogleService-Info.plist to the project (you can download it from the Firebase administration page).

If it works, you are done!

Plug-ins that depend on external libraries are often loaded by copying each external library, but if you copy and use the dependent libraries for each plug-in, you may get errors when using different versions of the same library (I actually did). So, I think it's better to use CocoaPods to manage all the dependent libraries (personal opinion). Some examples of dependent libraries are Firebase, AdMob, etc.

## Others
In addition to the above, I also created the following plugins

A plugin to display the review request dialog
https://github.com/funseek/godot-ios-request-review

Plugin to show ATT dialog
https://github.com/funseek/godot-ios-att

After I wrote this, I realized that it would be easier to use the plug-ins if they were loaded by CocoaPods. I thought. I'll try it next time.

I made an app for Scissors Shogi.

Akio Yamazaki — Sun, 23 May 2021 00:05:35 +0000

What is Scissors Shogi?

Scissors Shogi is a game played with Shogi tools, using only foot soldiers to remove the opponent's pieces.

See the following link for the rules
https://www.shogi.or.jp/knowledge/hasami_shogi/

Features

Computer games, online games, and friend games are supported.

Technology used

The game uses Phaser3.
PlayFab and Firebase are used for the backend.

Link
iOS
https://apps.apple.com/app/id1542437319

Android
https://play.google.com/store/apps/details?id=jp.co.kotakestudio.hasami

Web
https://necohasami.com
Web is still only available in Japanese. If there are many requests, we will support English as well!

We created a service to make API specifications easily.

Akio Yamazaki — Thu, 21 May 2020 07:04:05 +0000

Introduction

First, let me briefly introduce myself.
I am the CTO of a company called Funseek.

The company's main business is commissioned development, focusing on websites and smartphone applications (iOS and Android).
Recently, the development of websites as well as smartphones have been developed with SPA, and the server side is often processed by receiving responses on the front side with only APIs.

The main part of my work will be architecture selection, design, and source code review.
In this section, we will write about how to create a design document required for API design.

How do you create the API specifications?

I think Swagger, APIBlueprint, etc. are famous for creating API specifications.
I also used to use Swagger and APIBlueprint to create API specifications.
Other than that, I think there is a pattern to create in a free format using your favorite apps such as Word, Excel, etc... (I used to create them in the early days using Google documents, etc.)

Problems

Swagger and APIBlueprint (or any other tool) have to follow their own description rules.
Of course, if you remember the rules, you can easily output the API specification to HTML, PDF, etc., which is very convenient.
At first I was very happy with this.
But after a while, when I tried to write an API specification for another project, I opened a text editor and tried to write it. I've forgotten how to describe it. It always starts in the form of reading the documentation and processing the EXAMPLE. Yes, I always stumble on the starting dash.

So, why not just write it in free format?
In the beginning, I used to write using Google documents. The bad part of this is not limited to API specifications, but I am concerned about the formatting. Fonts here should be a little bigger, rules should be drawn, colors here, etc... The biggest problem with this one is that it takes up a lot of time for non-substantive work.

What you really want to do

Most API specifications have a specific format.

API name and outline
Endpoint
Contents of the Request
Response Content All you have to do is determine and fill in the following

You don't have to learn how to write your own, just fill in the fields and save. If you share the link, other members can see it with one click (in a nicely presented state, of course).
What I want to do is something as simple as this.

That's why I made it.

https://apibooks.funseek.co.jp/.
It's called APIBooks.

The concept is.

No unique description rule
Easy UI operation
Easy to share with links

is.

 You can focus only on the essential tasks and, as a result, save time!

What can you do?

The API specification is completed only by filling in the summary, Request, and Response items in the input field.
The duplicate function eliminates the need to create a similar function from scratch.
Input aids are provided for fixed items such as headers.
You can create as many API specifications as you like.
Can be shared by multiple members.
Importing the existing yml (OpenAPI 2,3)
Easy sharing by issuing API specification URL
Download the API specification as HTML.

At the end.

APIBooks is still a beta version with minimal features implemented.
All the features are now available for free! We'd like to continue to improve the service, so we're looking forward to your feedback!