Changes in Existing React Native App

[A] App technology: Existing app is developed using react-native-cli, node.js, and fetches content/data via APIs linked to Wordpress backend. App is hosted on 2 VPS servers, where DB is hosted on a separate VPS and Wordpress on the 2nd VPS. Both servers are connected and root access is available just like a dedicated server.


[B] About the app: A sports news app, which has different sections such as newsfeed, photos, memes, videos, etc. Each post on the app has a reaction bar with 4 reaction buttons and a comment button. All the content for the app is made in form of "posts" on Wordpress as a backend, which is fetched by the app's frontend via integrated APIs. App is using Firebase to send push notifications and FB analytics custom events. App supports Facebook, Google, Apple ID & Email logins, which are well integrated.


[C] Scope of Work: Following changes/modifications are required in the existing builds on both Android & iOS:

1. In-app purchase : Lock 3 sections in the app, which will be available only to "Pro-users" who will make the in-app purchase (single in-app purchase product on both Android & iOS builds, which opens all 3 sections for the user, monthly subscription on both Play Store & App Store).

2. New section in the app : In addition to existing sections of the app such as Photos, Videos, etc. a new section needs to be developed and integrated in the app's user menu, which will open natively within the app. This section will have a small logic based game which will enable users to make a team of their 5 favourite players* from the list of players shown to them. After they make their teams, they will not be able to edit/change their "fantasy" team, but will only be able to check the latest cumulative score of their team which will be updated as and when we update points of players* in the backend. We will have an option to "Reset" game, when all users will be able to make new teams, and everyone's score will be re-set. Leaderboard will be shown only to admins in the backend along with user's data in Wordpress. (More info. about this section can be shared with you on request)

3. In-App Immediate Update Module (Mandatory update) : In-App Updates needs to be set up for both Android & iOS users. Currently the app does not have this module integrated. This will help us force future updates on all users as and when critical updates are needed, the app won't work until updated to the latest version.

4. With reference to point #3 above : Disable existing APIs, by rendering an "App Update Required" image, and set up identical new APIs with new names and link the new APIs with the new build, so that upon the app update being available on Play Stores, we can manually disable old APIs from backend and ensure that all users update their apps, since mandatory update module is not configured in the current build. If we don't disable existing APIs then old users who don't update the app will still be able to access the "locked content" in the new build.

5. Google Analytics Custom Events creation & integration. All custom FB events which are currently integrated need to be replicated in Google analytics.

6. Facebook oEmbed integration for fetching FB & Instagram photos via access token.

7. Fake react-counter for every post/article on Wordpress, which can be edited from backend, and will also register genuine user reactions in addition to fake count. Also show reaction count permanently even before the user reacts. (unlike now when count is shown only on registering a reaction)

8. Implement a token based mechanism to check users' last logins and define a logic that filters user accounts where last login was more than 2 months ago, and ability to delete inactive user accounts from the DB based on user's last logins.

9. Removing some sections from the app completely & rearranging app menu items.

10. Achieve an overall performance improvement in loading time when all the above changes are finalized and tested thoroughly.


IMPORTANT:

1. Timelines need to be adhered to diligently.
2. Consistent communication needs to be kept all through the project.
3. Cross device and extensive testing on real devices as well as on Browserstack needs to be done before project is considered delivered.
4. Bugs or errors showing to some users later on once the new build is live, will need to be fixed free of cost for a period of 1 month from the date of delivery of project.

If work is found satisfactory with minimal bugs, a permanent position might be offered to the respective developer. Please write back only if you have at least 25 free hours a week to work on this, and are willing to stick to timelines and to communicate on a regular basis.


PROJECT COMPLETION:
We would like the entire project to be completed in all aspects including testing and be delivered within a maximum period of 45 days (Saturdays & Sundays included).


Please write back in case of any questions/clarifications.