Good evening, I am trying to make an application that (if connected to one's Whatsapp account) allows one to calculate certain messaging statistics. I'm developing it with React Native, I'd like to integrate everything in a single solution within the Android/IOS application and avoid making a project where the App interacts via API with my server (where my NodeJS project lies). Unfortunately, this seems more complex than expected. Has anyone tried this yet? Do you have any advice for me?
#WhatsappWeb.js + React Native
torpid fulcrum
vernal gale
I didn’t worked on anything such with WhatsApp but for backend functionality api is the best choice
torpid fulcrum
I know, but that's too easy and I wanted to do something integrated and end in itself that I could sell/distribute... maybe I should try api business? or some other kind of language instead of react?
Alternatively do you know if there is any way to integrate NodeJS (backend) functionality as a component of the React app or some similar hybrid, perhaps it could work that the app itself if in one acts as a server.
vernal gale
maybe using firebase then traditional API method.
torpid fulcrum
I had also thought of a similar solution, but I wanted something more personal. Anyway, thanks for the advice! I'll try to leave the ticket open another 1/2 day to see if anyone gives me any more ideas.
unreal rivet
I used nextjs for web. But not developed native app.
I wanted to create apis with type safety and I needed my backend has multiple things to handle. User payments, user plans, messaging limits as per plans, and multiple whatsapp instances which automatically creates and destroys as per users usage to minimize server load and most of basic functions like, whatsapp chat page with subscriptions, live messages, media upload, view, scheduling messaging with queue system to deliver messages.
It's running stable from months and all functionalities working pretty good with no issues. It was my personal use project just to experiment.
Backend am using nodejs express server with graphql. I didn't use apis because I had to write lot of apis and I lost keeping track of changes I make at backend. And it started to break at frontend. With graphql I can write api logic with assurance that api endpoint exists and am asking and getting correct data. I also prefer using trpc. But not for this project. Also working with qraphql hooks with react based projects is much easier then traditional apis.
And using redis for caching most common database details and api responses. Mainly using redis for Bull message queue management.
And database is mongodb (mongoose)
It's all within one turborepo. Keeping both frontend and backend at one monorepo is much easier to develop with type safety if you working alone or who develops both frontend and backend. And obviously am using typescript.
I think I can directly add react native to my turborepo and use same graphql apis for native apps also from same repo. I will also get same type safe apis. Will try this for sure.
naive tundra
Hi