Which architectural solution to choose for mobile access to 1C?

Question

Mobile development

Good afternoon,
Platform 1C8.1, the configuration is 70% self-written. 1C receives data from outside (several different types of servers with external systems, through which data regularly flows into 1C. 1C actually reads data from external services, starting automatic processing every 5 minutes).
Task: to make sure that employees (30 people) can work with it from their mobile devices (Android, iPhone, iPad) at least in limited functionality mode.
Interested in a view from the outside on exactly the possible architectural solutions, we will go through the details on our own.
From the options I see:
1. Write a web application, ~ equally well supported by Android, iOS, which will interact with 1C. The question here is how to organize the interaction of the application with 1C? Directly or through a separate SQL database with queries? The option with queries through a separate SQL database seems too cumbersome to me. The option directly raises the question - is it possible?
2. Write a native application that will interact directly with 1C using some adequate protocol. In the application, the essence is to implement only the interface, leave all the logic on the 1C side. The question is - will it be adequate in terms of speed?
3. Display 1C in a web application using 1C. It seems to be possible, but advice is needed here - how adequately and quickly will it work? Will it be cross platform?

Answer 1

If we are talking about 1C, then it is better to do everything exactly as 1C-nicknames themselves advise, and not to "sculpt a hunchback" from their protocols and applications.
8.3 has come a long way in terms of mobile zoo support, but a lot can be done within 8.1. For example, example one , example two - built-in platform mechanisms, there is authorization, data is generated directly by the platform (accordingly, everything that 1C allows you can do with the data), the finished page is given by the web server (apache, nginx, etc. - respectively with protection

from script-kiddy and ddos

). Again, the development of mobile functionality remains the responsibility of the one who develops the functionality of the application solution.

Answer 2

Is the option with 1C 8.3 and a regular (within the 1C platform) tool for creating mobile applications for Android / iOS not considered?
UPD : if anything, it's about this - www.v8.1c.ru/overview/Term_000000818.htm