Technology stack for mobile based internal tools - mobile

I'm building an mobile based internal tool for a company. But I'm not able to figure out the programming stack to use. I mean, I have read that only native, hybrid or web based apps can be built on phones but I'm not looking for web based and we don't want to bring the app to the app store since it's only for the company people. Any suggestions on how to approach here?

Related

Is it possible to sync a user from a MERN stack app with a Wordpress site?

Ok, so I have a Web Application that is built on the MERN stack(FE uses React and BE uses Express). I have a separate site that is built on WordPress that will be used as a knowledgebase/help desk site. The WordPress site currently is used used to have documentation articles, so it is not a problem, but later on, we would like to integrate a ticket system, as well as a forum. The main goal will be to use it for users to have a wide array of places to either get their problems fixed or to find a solution.
So based on that, is there a possibility to sync WordPress users with a MERN Web Application?

how do i decide technology stack for my platform?

Please help me out i am willing to create a platform for online education guide.i want a mobile application as well as web app both should use same data and backend i have decided to go for react native to develop mobile app and react for web i am confused about backend. in future i want to stream videos on my platform also Q/A section,comments,chats etc. what will be the suitable technology stack for my platform mainly what combination of database + framework should i use.
Chose your database tool for React Native Application - Read Here
Chose your Back End framework for React Native Application - Read Here
Note:
Since React/ReactNative both are JS Based you can simply use Node JS as back end framework and MongoDb as database tool simply.

Limitations with socket.io?

I am planning to use socket.io inside a hybrid mobile application packaged for a mobile device. Are there any limitations that I might encounter with browser adoption or anything of that sort? Will this sort of a set up work with all mobile devices when packaged and distributed?
Updated details
I am going to use it to write a chat application. If I do a basic chat application using socket.io and then package it using PhoneGap or Cordova/Ionic, would there be any issues with compatibility or can I expect all the features to work seamlessly?

web apps vs mobile apps

Is there a significant advantage of creating a mobile app as opposed to a web application?
I pose this question from the following perspective, which is biased towards my lack of knowledge of the mobile phone architecture.
You can build a web application with pure javascript, css, and html.
You don't have to write different code for iOS, Android, etc.
The user simply goes to a url, and that's your app, served right there from the server.
I would like someone to highlight some of the advantages of writing specific code for a mobile web application.
What does a mobile app fundamentally have a significant advantage over a web application?
Mobile apps have some advantages:
Assets are packaged on the phone - you only need to load data from
the server, not your layout.
Users are familiar with the conventions of their chosen mobile OS,
which your app will follow.
Trends show users are spending more time in Apps than web on mobile
Can work offline (even if limited)
Mobile apps have access to native features like push notifications,
GPS, Camera, etc
There are also hybrid apps - which are web apps running in a native container. You may have heard of Cordova, which is a platform for acheiving this. You basically create your app as a web app, and it runs inside a native WebView - with this you can use a javascript API to access some native features, but you don't get many of the other benefits of a native app.
Easy to use
Use native mobile design
Don't take long time to load just load data and images but web load (data/images/css/js)
I am not very experienced with this topic, but these are some fundamentals of using mobile apps:
They are accessible offline. (but that is restrictable)
The assets of the downloaded app are stored on the phone itself, thus the main content loads much faster.
As stated before, they have access to the hardware of the device (GPS, camera, etc, sensors etc.)
You can store as much data on the device as you want (opposed to, let's say 5mb using the HTML5's Local Storage).
They have access to push notifications (such as in Android or iOS)
They can put all the powerful hardware of the phone to use.

Reading Google App Engine's datastore to a native app

Does anyone know if it is possible to read from a Datastore on the app engine to a native app?
I am working my way through making a simple notes app that I can store online and use on my phone and tablet. I would prefer the phone interface be more than just a WebView instance or only used from the browser. I would also like a tablet optimized version as well.
I am comfortable programming android, and I am comfortable with web apps as well, so this is the last important piece before I can start putting it all together.
Has anyone done this before? Or, if it isn't possible, can someone send a link so I can further explore and find out what?
Thanks!
You can interface directly with the datastore using remote_api, but this is designed as an administrative interface, and shouldn't be used for access by end-users. The standard approach for what you're doing - on any webapp, regardless of platform - is to define an API that your application exposes for access to the data, and consume that API from your native app. If you're using Python, you may want to check out ProtoRPC (now included in the SDK) as an easy way to define APIs.

Resources