Geek Answers Handbook

Best practice discussion: when do you prefer web browsing through your own user interface in titanium?

I am currently working on a cross-platform mobile application and have gone through the process of creating a user interface for my application using this Titanium api.

Compared to when you create a mobile web application, this is a time-consuming task, because you do not have the ability to work with a visualized interface, like on a rendering web page using firebug.

Especially the creation of the form is annoying, so I decided to create my forms using html and make them in Webview, which turned out to be pretty nice for several reasons:

  • WebViews automatically scroll, so the soft keyboard will not close the input fields in your HTML form.

  • You can control what type of keyboard is displayed in the WebView form by setting tag attributes <input>.

  • You can use JavaScript libraries to add form validation, highlight fields, etc. into an HTML form.

While this works like a charm, and the titanium documentation encourages you to use webviews to create forms, I have mixed feelings about mixing your own user interfaces with webviews.

My questions to you:

  • What do you think of mixing your own user interfaces with Webviews?

  • Do you have other options for using Webview?

  • What can be the general criteria for using one or the other?

Thanks in advance:)

+2
source share
1 answer

Webviews?

: ? , Titanium/Native. Webviews ( ): , PDF Titanium: Android PDF "" ( ), PDF Webview. , WebView.

Webview?

, Webviews, : , -, , . . , (, Titanium), , PhoneGap, WP7/iPhone/Android/BlackBerry.

?

? , Titanium WP7. , , Titanium/Native apps. , , PhoneGap.

+2

More articles:


All Articles