A team system that supports the evolution and change of AbemaTV that breaks long-term development

AbemaTV's development department currently has about 50 people

Mr. This time we are talking about a mobile app client. I would like to start by talking about the mobile app development system and development process.

To introduce myself briefly, I am Hato, an iOS engineer at AbemaTV. thank you.

(audience applause)

As for the agenda, at first it was roughly ``How does AbemaTV's iOS team develop?''. There are 10 people now, but I would like to talk about what kind of system we are developing.

First of all, regarding the development system, AbemaTV's development department currently has about 50 people. From left to right, it looks like Director, Server, Design, Web, iOS, Android, QA. Also, each team will have a representative and a board member.

iOS will be a part of that, but even within that, the team is divided. We are divided into four major teams: the video team, the growth team, the essential improvement team, and the TV device team.

It's the iOS team, but as I said earlier, it's currently a team of 10 people. At the beginning of the launch, there were about 4 people, so it's going to be a lot more. Here, I got permission from everyone to show their faces, so I'm posting it (on the slide).

It was roughly divided into four parts earlier, but if you divide video, growth, essential improvement, and TV device (by member's face photo), it will look like this.

AbemaTV currently supports devices such as PC, iPhone/iPad, Android/tablet, Apple TV, Android TV/Amazon Fire TV, and Google Cast. The iOS team is in charge of iPhone/iPad and Apple TV, and Google Cast has a receiver on the TV side and a sender on the client side, so it falls under the responsibility of the sender side.