android - Which is a better method for me to make my web app usable on a mobile -

-

I have a web app that uses html and javascript to display (graph, report, table) and Sometimes the data is updated which is being queried and controlled by using a Tomato Java Controller and stored in a MySQL database. There is a lot of data in this DB and it gets more data on a daily basis.

Now I want to make it usable on both Android and iOS. The easiest way to do this, in my opinion, would be to create a web app just for a mobile device.

But those people who said that they are always better to develop it as a native app for both platforms.

I have also got a fourth option to develop an app for both at the same time, such as ... • C # -

• Java -

• Web API (HTML, Javascript) -

• Titanium (HTML, Javascript) -

I now have a lot of options and I really do not know that How to choose. I mean, why would not I choose the easiest way?

Any advice?

There may be a lot of bias in answering this question. However, there are some non-bias ideas that will help you progress properly.

  1. If you are unsure of mobile experience, user traction, etc. and you have no other barrier or requirements (i.e. you do not have any boss or board director who Level solutions), then go with the easiest route.

  2. If you believe to adopt a user of your site / app, but you are not skilled or do not have a budget for the original app, with the cross-platform tool Go. This will display your app in most markets with minimal effort.

  3. If you have a lack of design for basic platform development (i.e. the need to access native features) or business requirements (i.e. your boss says you have to do ), Then go with the original development.

Many people can argue for any kind of bias / logic, if you are going to an unrestricted market fundamentally, cheap, fast and easy start Doing is best. Development for mobile is completely different for development of desktop / web access. You will probably learn a lot and you have to make many adjustments in the requirements and product direction as you gain experience in the mobile market. When I am a big fan of original development, I probably will not do that in your case, which you have said so far.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more