Is there a reason why you would like to have passport.js integration. While it is a great lib for developers to implement authentication within an express app it is not a full authentication library. With passport you still have to implement all the logic yourself.
As for the original topic about using NodeJS for android backend. The NodeJS should work just as good as the PHP version. I see in most replies that the cookies are causing the issues, in NodeJS they can be configured using a user_config.json and in PHP it depends on the server configuration. In PHP you configure the session cookies using the php.ini file.
I always thought that it was a general problem with cookies on android related to the webview implementation. If PHP sessions work and NodeJS do not then we have to check what the difference in the cookie settings are. Maybe it is something simple like perhaps the httpOnly flag.
For us its more tools in the box and allows for flexibility and choice for our Clients. We have looked at it for a while now and we'll probably go ahead and create some Extensions for it to take advantage of its numerous integrations. If not just to save time but to improve overall security and User Experience within some of our Applications, that is part of the appeal to us.
Yes it absolutely does, and works great! Initially I did not know if it would work and faced some issues and assumed it could be the Server Model I was using as all previous mobile applications we have developed had a PHP based back-end. After some head-scratching we got everything to work, we'll put that down to teething issues and not having developed for mobile in a couple of years or more.
This was part of the issue but was more Security Provider not functioning correctly, which in no way was a bug or fault with Wappler. Was purely down to configuration and Capacitor's idiosyncrasies.
We thought this initially. I'm sure it is something simple. For us we do not mind scratching around under the bonnet. For new Users trying to create their first mobile applications it could be off-putting though as it is not really no-code or even low-code. It can get messy and confusing. For those of us accustomed to trying out different approaches this is not an issue, we are used to it. But again for those not familiar with it they will go around in circles. So yes maybe it could do with a little investigation and slight improvement for simplicity sake. Overall though we had no issues getting Wappler to build and run Android applications out of the box. Previously we had to implement a lot of ground-work before even attempting this (in Ubuntu), then we could only run the applications in Android Studio. Now it is all within Wappler and is flawless. Very refreshing having just returned to using Wappler for this purpose.
Once again @patrick I really do appreciate your response, insight, and direction. Thank you.