I’m involved in a Xamarin/Android project and very interested on alternatives for Android projects.
How will Wisej.Mobile work? Apps will use WebView and PhoneGap/Cordova?
The foundation is the communication layer (client, server, events, state, diffing), session management, component management, designer rendering, and all the base classes in Wisej.Core.dll and Wisej.Core.Design.dll. Wisej.Mobile.Control class will have Wisej.Base.ControlBase as the base class, which extends the single WinForms class (we don’t use any subset of winforms controls) that we use at design time for the designer. Data binding is also shared from Wisej.Core.
This thread is really important for us at HRTMS.
Do you have any idea on the time frame for a mobile offering? We are looking at Angular 2.0 as an alternative, but really like the productivity of your tool.
Its a such a difficult decision since we are unsure of your timeline.
Thanks in advance,
The equivalent of APK for iOS are .ipa (http://stackoverflow.com/questions/10808451/what-is-the-equivalent-of-apk-in-ios).
Another very important note on Android development: popups are shown asynchronously, meaning code execution continues after showing the popup (if your code shows 3 popups, the latest one will be on top). VWG did work like that on pre version 7.
1) WebView is like the windows forms WebBrowser control. As you can read on https://developer.android.com/guide/webapps/webview.html
“If you want to deliver a web application (or just a web page) as a part of a client application, you can do it using WebView. The WebView class is an extension of Android’s View class that allows you to display web pages as a part of your activity layout. It does not include any features of a fully developed web browser, such as navigation controls or an address bar. All that WebView does, by default, is show a web page.”
3) According to Luca’s previous answers, Wisej.Mobile is like Wisej.Web but using mobile controls instead of web controls.
4) Yes, just like any other APK.
5) Not as soon as we all want 😉
If you must go for native developement, be prepared:
Estimate time as you would do for a Wisej.Web project, then multiply by… it depends on the project size.
If the APK must run everywhere, you must have a generous maintenance contract so you can update the project whenever your client finds a very cheap tablet that has some issues with your app.
Now I understand why there are so many updates on mobile apps. It’s not about new features; it’s about new devices.
I expect Wisej.Mobile to take us back to the more normal web world. 🙂
Hi Tiago and Luca,
A few days ago I was asked to give an estimate of time/cost for an application that will run on Android and iOs… And since I wouldn’t like to start learning native development right now, I would like to ask some questions from a completely illiterate’s on mobile development point of view:
Wisej.Mobile will use the same foundation (Wisej.Core and Wisej.Core.Designer) of Wisej.Web but with a new set of controls and a designer surface adapted to mobile phones and tablets. This is the set of controls, you can try it here: http://www.qooxdoo.org/devel/mobileshowcase.
We’ll probably extend the themes either using the current ThemeBuilder or something similar.
The end result will be a web site that can be used standalone or with PhoneGap. Additional native platform coding to use WebView, properties, installation, etc. is outside of the Wisej.Mobile scope.