Uber Eats and Lyft separate applications - mobile

I was wondering if anyone knows the reason why Uber Eats, and Lyft have two separate applications for users and drivers.

Related

Mac Os Core Data App that shares database between two computers

I made a mac os app (with a large database implemented with Core Data). This app is private, I use this app only for my job (it is not sold on the mac app store). Now I would use this app from two different computers (two users) and it would be great to share the database between two users.
How can I make this?
I know about Cloudkit, but it is necessary to pay Apple development program to use it.
Is there any other solution, perhaps (free and) more easy of Cloukit?
thx
Core Data is designed to work as the local data store of a single app. Apple’s CloudKit is the only way it really supports syncing. You could try putting the data store in a folder synced by Dropbox, iCloud Drive, etc, but it’s unlikely to work reliably. If getting syncing in your app isn’t worth $99 to you then you probably need to look at third party solutions like Firebase, but that probably means redesigning the app to not use Core Data.

Developing Spring based Restful webservice for enterprise level application and mobile application

Need help in developing an Enterprise application which involves hundreds of thousands of notifications and calls to server. Client has mandated to use Java/Springs stack. It has 3 portals involving like mobile, Institutes and Admin which depends on web services from server.
Which type of Database we should prefer?(It should support Hundreds of requests and Should support Geo-Location based queries)
Which application server we should prefer?
Which type of server side scripting we should prefer?
How about should I go with this?
You really should read the answers to this: https://gis.stackexchange.com/q/9809
One you know it or have anyone in your team who knows it. Otherwise WildFly seems pretty good.
Once again you must choose one you're comfortable with... and look at Thymeleaf.
If you are really starting something from the ground, you really get known the Service-oriented architecture and build your solution around it.

Mixing aws and app engine

We are starting a new project that requires two main components:
Backend for task management, e.g retrieve a task from a queue and according to some specific logic validate it.
Run a real compiler on that specific task and create an executable that an end user should receive.
We love app engine, however the second part will require a concrete instance where an actual compiler will have to be installed, app engine is not capable here. We were thinking to mix both app engine and aws instances to accomplish the task (part 1 will be app engine and part 2 will be aws).
All of our senses say it's a bad idea:
unneeded traffic between the two providers, someone needs to pay for that unfortunately.
We'll have to deal with two systems, two deployments process, each system has its own quirks --> double the work.
But we love app engine.
Does anyone has any experience in combining the two systems? any recommendations ?
There's no reason why what you suggest won't work, especially if you separate your concerns well, by exposing a clean 'compiler' interface on AWS or a similar service. Yes, you will have to pay for traffic between the two services, but this is unlikely to be substantial. If you are serving up the end result to the user, you can link them directly to AWS, rather than fetching it with your app first.
AWS's EC2s are literally just vanilla linux boxes in the sky. I would also throw out the suggestion of just moving to it completely. Porting your system over may be easier than it sounds if you're unix savvy.

Distributing an application across Internet

I searched but couldn't find a proper answer for this...may be I didn't look deep enough. Anyways, little insight from you guys will only make things easier. So hear me out.
this is for my final year research project. I just need concepts and if any links I can read more.
So this application is a distributed one for a hotel which has 3 branches (including the main hotel) in location A, B, C.
I & (my colleagues) have developed the database, business logic, and 3 separate GUIs for the billing, bar and the kitchen. All are working perfectly and we used .NET remoting for this. this is the whole system and GUIs connected to the business through LAN.
This system, should be deployed in each location (A,B,C) and from the main hotel (A), I should be able to view the details of other locations (B,C). and all 3 systems should be connected through the internet.
problem is, how do I do that?
I just wanna view the information of other places and may be take printouts. that is not relevant for the question i guess.
The database is not distributed, each location has its own database. If I were to use a web service, how can I do it more cost-effectively? where do I have to deploy the service?
as a side note, I have developed a simple chat system (remoting) and tried to connect it through internet with a friend but it didn't work. If anyone knows why?
please be kind enough to provide any other relevant information on this topic. and please ask questions.
Why not just build a web application with a secure login? That way you build one system, deploy one system, maintain one system. All your data would be in one place, making reporting a lot less onerous, the whole thing would be faster and if you ever need to add a fourth, fifth or twenty seventh additional location, then you'd need to do very little to make it happen.
I see no reason why you have to go about it as you are.

windows application with web access to database

I want to write several programs with the same database. I have two solutions:
developing programs as windows application and using web service for access to share database. (may it cause, the speed of windows applications down or not?)
developing programs as web application
which way is better?
Thanks
Which way is better
Which is preferable depends upon the requirements you're developing the applications to.
If your users are on a variety of platforms (Windows, OSX, Mobile devices), or you don't want to deal with application deployment problems then a Web application may be best.
If you need to access features of the operating system (client side processing, data storage, etc) - then you may need to use a deployed application.
You should look at what the requirements are more closely, which will give you the answer.

Resources