Database Info

[Q] Which Tool Is Right for Me?

I'm wondering, based on experience witch of these people would recommend for mobile app development. (Please mention which of these you actually have experience using.)
I'm an "old school" developer and am proficient in PHP/PERL, HTML, CSS and Javascript. I don't have time to learn a new language like C# and I refuse to use Microsoft's tolls (like .NET, Visual Studio, etc.) but I would spend the time maybe to pickup up RUBY (or maybe Java) if enough benefit was there in the associated mobile app development tool.
I want as close to native as possible with 90%+ cross-platform solution, meaning, 5-10% of the source code may differ due to differences in platform. I will only be developing for Android and IOS (sorry Windows) but may develop for Windows Down the road. Some apps I may develop may be enterprise class that need to get remote data from SQL Server, etc. I have done research and narrowed down my selection and am looking for further insight from those that have actually used these tools. Things that are also important to me include:
- Low cost (I can't afford to pay $100+ a month in fees)
- Good/Large Developer Community
- Good Support from Maker (good roadmap with improvements, bug fixes frequent, etc.)
PhoneGap - This seems like the most popular but it sounds like the "quickest" route for most web developers that are familiar with HTML and Javascript/CSS but to me it sounds like I might want something that is closer to native being that my primary core knowledge has always been as a coder first, and a web developer/designer second.
Appcellerator Titanium - This seems like the other most popular tool that claims to compile so the app uses the devices native controls (via Titanium API) instead of essentially an HTML page masquarading as an app (like PhoneGap) My gut says this one suits my situation better than Phonegap. Why do people use PhoneGap instead of this, because it's easier for non-programmers?
RhoMobile Rhodes - I am wondering how this compares to the two above assuming I learn RUBY on Rails.
Telerik Icenium (now called AppBuilder) - This one I have found the least discussion about.
I just ran across Codename One too which sounded intriguing as would require me to learn Java.
It seems most everyone (that isn't doing native) is using PhoneGap or Titanium and the second two are lesser known so I'm having a hard time finding people that has at least some brief experience using all four or five of these.
Any insight is greatly appreciated.

jazee said:
I'm wondering, based on experience witch of these people would recommend for mobile app development. (Please mention which of these you actually have experience using.)
I'm an "old school" developer and am proficient in PHP/PERL, HTML, CSS and Javascript. I don't have time to learn a new language like C# and I refuse to use Microsoft's tolls (like .NET, Visual Studio, etc.) but I would spend the time maybe to pickup up RUBY (or maybe Java) if enough benefit was there in the associated mobile app development tool.
I want as close to native as possible with 90%+ cross-platform solution, meaning, 5-10% of the source code may differ due to differences in platform. I will only be developing for Android and IOS (sorry Windows) but may develop for Windows Down the road. Some apps I may develop may be enterprise class that need to get remote data from SQL Server, etc. I have done research and narrowed down my selection and am looking for further insight from those that have actually used these tools. Things that are also important to me include:
- Low cost (I can't afford to pay $100+ a month in fees)
- Good/Large Developer Community
- Good Support from Maker (good roadmap with improvements, bug fixes frequent, etc.)
PhoneGap - This seems like the most popular but it sounds like the "quickest" route for most web developers that are familiar with HTML and Javascript/CSS but to me it sounds like I might want something that is closer to native being that my primary core knowledge has always been as a coder first, and a web developer/designer second.
Appcellerator Titanium - This seems like the other most popular tool that claims to compile so the app uses the devices native controls (via Titanium API) instead of essentially an HTML page masquarading as an app (like PhoneGap) My gut says this one suits my situation better than Phonegap. Why do people use PhoneGap instead of this, because it's easier for non-programmers?
RhoMobile Rhodes - I am wondering how this compares to the two above assuming I learn RUBY on Rails.
Telerik Icenium (now called AppBuilder) - This one I have found the least discussion about.
I just ran across Codename One too which sounded intriguing as would require me to learn Java.
It seems most everyone (that isn't doing native) is using Cordova/PhoneGap or Titanium and the second two are lesser known so I'm having a hard time finding people that has at least some brief experience using all four or five of these.
Any insight is greatly appreciated.
Click to expand...
Click to collapse
Both Phonegap and Appcelerator compile into a native package containing a mix of native and javascript and with both you develop your code using Javascript. As you've pointed out, one of the key differences is that Appcelerator will use the native device OS widgets rather than web widgets. In simple terms the layout is abstracted into an XML format which is then rendered into native equivalents during compilation for each of the platforms.
Depending on your application, native widgets may be important, or not. For example if you're developing a game then it could actually be advantages not to use the native widgets and have an essentially identical look and feel across all device platforms and screen aspect ratios.
The other difference is that Phonegap is free, (though their optional build service is not). Appcelerator is priced on a monthly subscription, but you also get some cloud features included in that.
Other popular cross platform tools to check out: Xamarin (native widgets, C# development, non-Free), ReactJS (native widgets, Javascript development, free-open source)

You can also try using Ionic and Cordova frameworks, They support cross-platform development and in my opinion have good documentation support

Mobile application development platform: how to choose best one?

There are many Mobile application development platforms available in the market; but which one you should choose and to which platform you would give priority?
Are you seeking for the right Mobile Application Development Platform for your job? Has your organization recognized mobile applications as a key part of your approach? Smartphone app development is blasting each single day and leaving developers challenged with a plenty of varieties for app development platforms. Since app development can be a money-spinning business, new app developers wanting to build up the next big thing. Mobile platforms have sprung up throughout the years to provide to the expanding demand, however how would you pick which platform is best for your application?
If we discuss about today’s desktop application developers, they basically have three platforms to look over: Windows, MAC and Linux. What's more, that being said, there are often approaches to make software composed for one platform which keep running on the others. Similar to this mobile app developers also have choices to select the platform as per their prerequisite from iOS, Android, Windows and Blackberry. They can also utilize cross platform tools to build up applications.
Mobile apps are similar to any other product; if you need individuals to utilize it, it should be great. Excessive applications are always attractive, intended for performance and modified to convey the usefulness your client wants, on the go and in a freely-flowing manner. When choosing a Mobile Application Development Platform, be assured it can facilitate the app development that will address the exceptional needs of your association and your current as well as future clients.
Other element to focus in terms of picking a Mobile Application Development Platform is your focused audience. If your application focuses the Hugh ratio of business, you need to verify the most widespread platforms for example; iOS and Android are your needs. If the community of businesses is your essential target, commercial platforms like BlackBerry make a worthy selection. Either way, it’s very important to preserve your focused audience in mind when choosing your mobile platform.
Whether creating mobile apps is your desire or an interest, you will require income to endure your business. Consider the expenses and benefit before you get on the app development drive. When you choose a mobile technology, guarantee it delivers a powerful safety and verification structure. Such features comprise safe and protected client/server communication, on-device encryption, offline validation, access controller and other appliance that will complement your current structure as well as direct your brand away from humiliation and legitimate activities.
Most customers need to convey native apps, on both iOS and Android. By focusing on both the platforms you will be, apparently, success the entire Smartphone market. Thus, assuming budget is not a restricting component, it bodes well to handle iOS and Android together. If the application is a prototype app we would like to suggest Android platform to begin with, because there is no approval process with the Android App Store; this is absolutely a major advantage to Android if you are in a competition of market.
The mobile backdrop is a long way from standardizing. With the continuous fracture of gadgets and no strong leader in the business sector, organizations must keep on providing their applications to a range of OSes. Yet, to do as such, be mindful that the mobile structure which is at the center of your methodology must be upheld by a merchant who can rapidly help new surroundings as they achieve the business and enable you to spread out your abilities to come across the requirements of clients and staffs while changing your business for mobile achievement.
Before picking a Mobile Application Development Platform, get your work done. Think twice what decisions you have made. Look at how strong is the platform’s development surroundings? What number of handsets is accessible and what elements do they offer? Also check out Cloud adaptability, analytics and communication services, native, web or Hybrid, developer tools and resources Etc.

Cross-Platform vs Native

Hey,
I'm a developer and I want to start with app development. No games, just productivity stuff. Without experience, I would tend to native apps, because you can use all api's, designs etc. I think cross platform frameworks is just a hype like java for web. HTML and CSS are the best choice for web and nobody is talking about java in web-dev. Now, I have a feeling that you're trying to use this technology in Apps because html5 and css3 a fancy. But this is just my opinion and maybe I'm wrong. As I mentioned, I do not have any experience in app-dev. Therefore, I want to ask you, because you have the experience.
Are cross platform frameworks a great choice to develop apps for iOS, Android and Windows 10 (Mobile)? Is it really time saving and do I have the same or similar possibilities? Or is it better to maintain three different platforms? Maybe the time effort isn't so much higher. I don't know. How high is it? Should I start with a cross platform framework and switch later to native apps, or is it better to start with native apps?
I hope you can share your experience with me. It is also great if you link something that reflects your opinion.
Thanks
neon

"nobody is talking about java in web-dev"
Not true Many pages and server side app are created in java. JEE, JSF etc. Problem is hosting for page. Hosting for PHP is cheaper and more popular. That is why PHP is more popular than Java in web-dev.
Anyway, in mobile platform, in my opion, better way is native apps. Cross platform frameworks are great, but only for some of the types application. Most applications can be made faster and look prettier if they are native. Many things is hard when you use crossplatform, and sometimes development takes longer. Much depends on type of application and requirements. Of course it's only my opinion. Many people think differently.

It depends. First of all it is important to know which API or librarys you want to use. If you have some intensive tasks or calculations you should go with native apps because they are often much faster then hybrid-apps written in JavaScript. If you don't have much intensive tasks and you have a completely new idea and want to make money with it you shoud go with hybrid-apps because it is a huge plus to have an App for Android AND iOS.

Thanks for you responses.
@Asmok78
You are right. PHP is more popular because it is cheaper.
Asmok78 wrote that most applications can be made faster and it depends an the application. spcialx wrote something equal. So, as an example, all my ideas are based on a client server architecture where users can sync there local data with a server to work collaborativ. As an example it could be an app for all three platform (iOS, Android and Windows 10(Mobile)). A user can manage a tasklist and share tasks with other users, or you have a project and one user can assign tasks to other users.
I guess it will be faster to get a first working app with a crossplatform framework. But I also guess, that in the long run it will be better to dev native apps. So why not start directly with native apps?

ne0n said:
[...]
I guess it will be faster to get a first working app with a crossplatform framework. But I also guess, that in the long run it will be better to dev native apps. So why not start directly with native apps?
Click to expand...
Click to collapse
Your assumption is completely right.
I'm working on a hybrid app right now. While it can be tempting, as soon as you get out of common features and patterns you can run into all sorts of problems and I found some quite hard to debug and solve. In the end I've busted all my deadlines. Performance are just OK for most uses, but still not comparable to native. All in all it depends on what you are trying to do, cross-platform apps might be ok for some use cases, but native apps are well worth the extra effort.

I think you should go native for apps. But not for games.
Sent from Tapatalk. Try LucidPod - lightweight podcast player.

Android NDK is there for performance reasons. If you plan to create something serious, then dedicated development cycles for each platform may be the obvious choice.

with web app, you can create app with nice and easy ui, can communicate with system api via plugin but sometime you need custom there control, and you need experience with native app , if it basic, you can do with only web app.
hybrid app is slower than native, only for small app.

Asmok78 said:
"nobody is talking about java in web-dev"
Not true Many pages and server side app are created in java. JEE, JSF etc. Problem is hosting for page. Hosting for PHP is cheaper and more popular. That is why PHP is more popular than Java in web-dev.
Anyway, in mobile platform, in my opion, better way is native apps. Cross platform frameworks are great, but only for some of the types application. Most applications can be made faster and look prettier if they are native. Many things is hard when you use crossplatform, and sometimes development takes longer. Much depends on type of application and requirements. Of course it's only my opinion. Many people think differently.
Click to expand...
Click to collapse
Yep, I'm a java web guy. Tomcat, Struts 2 and JSP for me (though I'm slowly switching to Spring instead of Struts). The sheer power of Java, the stuff you can do, vs PHP (disclaimer: I coded PHP for 10 years professionally and now hate it, especially with the advent of Wordpress and Drupal) is absolutely staggering. Add to that a tonne of amazing libraries one can just plug straight in and you get a really useful bit of kit. Sorry, off-topic.
So yeah native is best. I work on a timesheeting/expenses solution for big mobile telcos in the UK and we looked at some cross-platform solutions at first, with Xamarin getting a decent run out but in the end we concluded it just wouldn't do the job, and went native. The issue really was that you'd end up with an app that wasn't quite right on either platform, and had to really write some nasty hacky stuff to make anything that took advantage of the advantages or preferred style of a particular platform. It just wasn't worth the effort in the end.

With Unity3d you can build for like 20 platforms.

Cross-Platform vs Native | Development Tools
1. Native apps are usually developed to work on a single mobile platform by using the native programming language mainly used for user interactions.
2. Cross platform requires different platforms for development are used for PhoneGap, Titanium, and Xamarin by using HTML and JavaScript mainly used for iOS, windows, and Android.

"no one is discussing java in web-dev"
Not genuine Many pages and server side application are made in java. JEE, JSF and so on. Issue is facilitating for page. Facilitating for PHP is less expensive and more mainstream. That is the reason PHP is more well known than Java in web-dev.
Anyway, in portable stage, in my opion, better way is local applications. Cross stage systems are incredible, yet just for a portion of the sorts application. Most applications can be made quicker and look prettier on the off chance that they are local. Numerous things is hard when you utilize crossplatform, and infrequently improvement takes longer. Much relies on upon kind of utilization and necessities. Obviously it's lone my sentiment. Numerous individuals think in an unexpected way.

whats the end goal/how big is your buget?
for example: business apps, they're not that heavy on interactions/animations - you may be better off with cross platform as it will generally cost less to create it that way
if heavy on interactions/animations: native would be a better choice and may cost more because it may be developed for multiple platforms, which in turn would make it more expensive.

Hi,
If you ask me I will go with the cross platform if I'm building the app from scratch as it's easier to make any changes and most importantly saves a lot of time.

5 Key Benefits of Native Mobile Application Development

What is Native Mobile App Development?
Native mobile app development involves building apps for particular mobile operating systems, and users access them from dedicated app stores (such as the App Store or Google Play).
1. Native Apps Have The Best Performance
With native mobile application development, the app is created and optimized for a specific platform. As a result, the app demonstrates an extremely high level of performance. Native apps are very fast and responsive because they are built for that specific platform and are compiled using platforms core programming language and APIs. As a result, the app is much more efficient. The device stores the app allowing the software to leverage the device’s processing speed. As users navigate through a native mobile app, the contents and visual elements are already stored on their phone which means load times are quick.
2. Native Apps Are More Secure
Web apps rely on different browsers and underlying technologies such as JavaScript, HTML5, and CSS. Developing a native mobile app is a great way to guarantee your users reliable data protection.
3. Native Apps Are More Interactive And Intuitive
Native mobile apps run much smoother regarding user input and output. These types of apps inherit their devices’ OS interfaces, making them look and feel like an integrated part of the device.
4. Native Apps Allow Developers to Access the Full Feature Set of Devices
Native apps are developed for their particular platform, taking full advantage of the software and the operating systems’ features. These apps can directly access the hardware of the device such as the GPS, camera, microphone, etc. so they are faster in execution, which ultimately results in better user experience. Push notifications are another huge advantage to choosing native app development. Push notifications go through the iOS server (APNS) which you need your app bundle ID and same with Google’s Cloud Messaging (GCM).
5. Native App Development Tends to Have Fewer Bugs During Development
It’s much more difficult to maintain two different applications in one codebase than it is two applications in two codebases. With native app development, you have fewer dependencies for bugs to occur because you’re not relying on a cross-platform tool such as Xamarin or Cordova. Hybrid apps access hardware through a bridge which often slows development down and can amount to a frustrating user experience.

Native vs Cross Platform

Hi everyone. I know that it's not a new subject, but I think it's a good subject to discuss about. It's the first question for any developer who wants to start a new project as everyday we can see new frameworks and languages comming up for development. After years of development now when I want to start a new project think about it again. It will be great if any one who has any experience can share it here. Because it's the experiences and times that show us if a decision was a good one or not. We can write about different parameters we considered to start a project, challenges and the results. Please feel free to add any other item you think is important to consider.
I start by myself:
Subject: A Network Communication App
Long/Short term consideration: Long term
Target platforms considered at start: android, windows
Target platforms implemented: after 2 years, android, windows, linux, (ios just newly started)
Framework: Qt5 (a cross platform framework)
Challenges: We used a crossplatform framework but as you know any OS has it's considerations and styles for development. Also different frameworks have different capacities for handling these features. In this project one of the challenges we had was the way android handles services and activities. We had to separate our UI from the logic controllers completely and implement a way to communicate between these separated processes. Also we had to implement the OS based features separately for each OS like notifications and alarms. Fortunately Qt let you use native codes for these specific features. For example you can use native java codes for showing a notification or playing system native sounds and alarms.
Pros: We implemented our UI just once and used it for all platforms. Also we implemented network and controller threads once and used them for all platforms. In this way if we need any change in our protocols or UI, we just develop them once. So we have one development team for all of them.
Result: Cross Platform with Qt was a good decision at that time for that project. Specially for a small team like what we had, because after you implement the base of a project like this you have to support it for a long time and add features to it. If we were using native codes, now we had to have separated teams for developing new features and supporting it.
It's great to read about other people stories. So Please let us know about them.
Thanks

Native vs. Cross-Platform
Native apps are developed only for a specific platform. These apps are formed in a language cooperative with the platform. Apple, for instance, prefers Objective C and Swift for iOS while Google supports Java for Android. Using these satisfactory languages, developers can create safer use of the inherent features of these platforms. A native app developed for Android will not function on iOS and vice versa.
Cross-platform apps are cooperative with various platforms. Due to the market share of Android and iOS, most cross-platform apps are confined to these two operating systems. These apps are produced in HTML and CSS since these official web technologies are platform-independent. Several cross-platform application development tools enable developers to create these apps with little trouble.