Lessons learned from closing a major product: NAVER MATOME

Michito Tsuneta
LINE Development Team N Project Manager
https://linedevday.linecorp.com/2020/ja/sessions/3939
https://linedevday.linecorp.com/2020/en/sessions/3939

Transcript

2. Knowledge of the closing process in large-scale products
3. NAVER MATOME
4. Agenda › Self-introduction › About NAVER MATOME › Tasks for closing › Problems › Lesson Learned › From now on
5. Self-introduction › Smartphone app ： Property search app, etc. › NAVER MATOME： Maintenance operation , New service development › Feature phone website：Site for M1F1 etc. Development 3 Center Service Development Division 2 development N team › Mainframe： Government system. ( COBOL ) › Client-server ： Government system, etc.（Pro*C, VB ）
6. About NAVER MATOME
7. history 2010 • First anniversary • Start incentive program 2009 • Closed beta release • Service Releases • Mobile Release • Announcement Feature release • Social bookmarking collaboration started • Start displaying the number of accesses • Smartphone version release About NAVER MATOME
8. About NAVER MATOME 2009
9. About NAVER MATOME 2010
10. history 2012 2011 About NAVER MATOME • Major renewal • iOS App Release • Save Draft feature release • Topic Features Release • Android App Release • Group Summary Feature Release • Commercialization • Commencement of incentive system • Sponsored MATOME Release • Favorite Feature Release • Official MATOME Release • Add Category, "Category Sponsored" Release • Official Picture Release
11. About NAVER MATOME 2011
12. About NAVER MATOME 2012
13. history 2017 2015 • Monthly PV·UB record (3.1 billion PV·75.62 million UB) 2016 • Always SSL • Introduction of "deemed non-display system“ • improvement in disclosure requests 2014 • Smartphone version design renewal • Renewal of incentive system About NAVER MATOME 2013 • Jack Advertising Release • Business alliance with Yahoo! Japan • [Favorite Feature] Renewal 2018 • Business Succession to Next Library • Author Rank and Lisah release
14. history 2020 • Service Termination Notification • Suspension of new membership registration • End of service 2019 • Corporate "Mega Reach Video" released About NAVER MATOME
15. About NAVER MATOME Yahoo! topic Yahoo! trend reaction
16. About NAVER MATOME Twitter trend reaction At the time of service end notification. 2020/07/01 At the end of service. 2020/09/30
17. About NAVER MATOME Numbers
18. Total PV 171.8 billion PV About NAVER MATOME Numbers
19. Monthly Maximum PV 3.1 billion PV Total PV 171.8 billion PV About NAVER MATOME Numbers
20. Monthly Maximum PV 3.1 billion PV Total PV 171.8 billion PV Monthly Maximum UB 75.62 million UB About NAVER MATOME Numbers
21. Total Matome 1.8 million MATOME About NAVER MATOME Numbers
22. Total accounts created 340,000 Total Matome 1.8 million MATOME About NAVER MATOME Numbers account
23. Max View 3 million View About NAVER MATOME Numbers
24. single-user- created 26,000 MATOME Max View 3 million View About NAVER MATOME Numbers
25. single-user- created 26,000 MATOME Max View 3 million View Service Days 4,110 day About NAVER MATOME Numbers
26. About closing
27. Tasks for closing
28. Tasks for closing Overview › End notification period, etc. affects closing time › Some items need to be reported to the government. › 270+ total tasks
29. Tasks End date determined arrangement of rules and contracts man-hour estimate of development required for closing Notification method, timing consideration For Users announcement, timing Suspend new account activation Review Help Page incentive review For Partners cancellation procedure close response man- hour estimate contract termination timing arrangement Tasks for closing
30. Tasks End date determined arrangement of rules and contracts man-hour estimate of development required for closing Notification method, timing consideration For Users announcement, timing Suspend new account activation Review Help Page incentive review For Partners cancellation procedure close response man- hour estimate contract termination timing arrangement Tasks for closing
31. Tasks End date determined arrangement of rules and contracts man-hour estimate of development required for closing Notification method, timing consideration For Users announcement, timing Suspend new account activation Review Help Page incentive review For Partners cancellation procedure close response man- hour estimate contract termination timing arrangement Tasks for closing
32. Tasks End date determined arrangement of rules and contracts man-hour estimate of development required for closing Notification method, timing consideration For Users announcement, timing Suspend new account activation Review Help Page incentive review For Partners cancellation procedure close response man- hour estimate contract termination timing arrangement Tasks for closing
33. Problems & Lesson Learned
34. Problems › When can the service end. › The end notice may not be posted. › Can't watch the video. › Sudden server down. › What happens to the ongoing project.
35. Problems › When can the service end. › The end notice may not be posted. → Case 1 › Can‘t watch the video. → Case 2 › Sudden server down. › What happens to the ongoing project.
36. Problems Case1
37. Problems › Three months before closing Release of end notice posted on iOS app
38. NAVER MATOME iOS App › Requires an end notice period of 3 months. › Refurbishment period and Apple review period required to release iOS app. Problems
39. NAVER MATOME iOS App › Requires an end notice period of 3 months. › Refurbishment period and Apple review period required to release iOS app. Problems
40. Problems Sign in with Apple
41. Problems Sign in with Apple 2020.06.30 2020.04.30 → The day before the end notice publication date.
42. › Anyway, I submitted a store application › As a result, the store will be released on 7/1. Problems
43. Lesson Learned
44. Lesson Learned › We should have considered more about the potential impact of the platform we are using on our services.
45. Lesson Learned › Cases where service refurbishment may not be in control of release should have been addressed with greater importance. › We should have considered more about the potential impact of the platform we are using on our services.
46. Problems Case2
47. Problems › One month before closing YouTube search problem
48. Create Matome Articles › Choose a YouTube item › Find and add Problems
49. YouTube API administration screen › Queries is... at 0 Problems
50. YouTube API administration screen › Queries is... at 0 Problems
51. Problems Must comply with YouTube API Terms of Service.
52. Problems Must comply with YouTube API Terms of Service. The necessary renovations are: ·Change logo and icon ⇒ OK ·Change in how to use YouTube API ⇒ I don't know immediately how long it will take. ·Changes to NAVER MATOME Terms of Use ⇒ I can't respond immediately.
53. › Failure within a month of closing Problems
54. › Estimate of completion of first proposal exceeds closing timing › Failure within a month of closing Problems
55. › Estimate of completion of first proposal exceeds closing timing › Failure within a month of closing Problems › However, there are not many users of this function.
56. › Then, isn't it okay for the month to end? Problems
57. The words that PM said at that time. › The service is still working. › There may be some parts that make you feel relaxed when you finish, but I want to tighten my mind again. Problems
58. › Eventually, another plan will be implemented to resolve the issue. › I was able to respond for a week. › It's not perfect, but it was a response that could be selected at that time. Problems as a result
59. Lesson Learned
60. Lesson Learned › Service in progress until service termination.
61. Lesson Learned › Think about what you can do. › Service in progress until service termination.
62. Lesson Learned › Think about what you can do. › Continue the service comfortably until the end. › Service in progress until service termination.
63. From now on
64. From now on › Experience and knowledge accumulated through NAVER MATOME will be transferred to LINE
65. Thank you