Big News: FounderDating is joining OneVest to build the largest community for entrepreneurs. Details here
Latest Notifications
You have no recent recommendations.
Name
Title
 
MiniBio
FOLLOW
Title
 Followers
FOLLOW TOPIC

Question goes here

1,300 Followers

  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur

Cross Platform Application

I want to develop a cross platform app for Windows and OSX.
What road we I follow, Java, C++ or some other framework?

Keep in mind that later on there will be clients for IOS and Android.

18 Replies

Freeman Fan
1
0
Freeman Fan Entrepreneur • Advisor
Entrepreneur
You might want to look into Adobe Air.
Brent Goldstein
3
0
Brent Goldstein Entrepreneur • Advisor
Bold, Multi-Disciplined Software Engineering Leader - I’ll transform your organization and deliver the products you need
Is there a reason it cannot be a web application? Client side web frameworks are getting very capable now. This gets past most of the platform specific issues beyond dealing with a few different browsers, which is easier now that it used to be.

-Brent
Steve Banfield
1
0
Steve Banfield Entrepreneur • Advisor
Chief Marketing Officer at INRIX
You can take a look athttp://xamarin.com/. It will let you do cross platform Mac, Windows, iOS, etc but the underlying code needs to be written in C#. Depending on your development staff that may be a learning curve for them.

I haven't used it so I can't speak to how hard it is to develop with, or the potential performance impacts of using it vs doing native code.
Matthew Szatmary
0
0
Senior Video Encoding Engineer at Twitch.TV
I have done this many times with great success using Qt.
Chipit Promotions
1
0
Chipit Promotions Entrepreneur
Software Architect
+1 for AIR
Jerome Dangu
0
0
Jerome Dangu Entrepreneur
CTO & Co-Founder at ClarityAd
+1 for Qt goodness.
WxWidgets and Gtk are other options. Java is possible too.
iOS and Android will require their own implementations.

Another way is to go full HTML, building the core client in HTML and light native wrappers (webview) for each platform. For desktop, Chromium Embedded Framework enables a similar concept as Webviews in mobile apps.
Dimitry Rotstein
0
0
Dimitry Rotstein Entrepreneur
Head of R&D at SafeZone
Each language has a variety of associated cross-platform frameworks, and it's hard (if not impossible) to say which language has better frameworks. So first I'd choose a language based on other factors, and then decide on a suitable framework (not vice versa). For Java the best one I know is CodeNameOne, though it's not exactly mature yet, and I'm not sure it supports desktops at all. Eclipse is supposed to be cross-platform too, or so I've heard. For JavaScript there arePhoneGap andAppcelerator's Titanium. And for C++ there is Digia's Qt, which supports Win and OSX, and should support Android and iOS soon (if not already). Embarcadero's FireMonkey seems to be not bad as well (at least at a first glance - haven't really looked much at it) and it supports Delphi (for some reason) in addition to C++.There are a few dozen other frameworks I know of, but they all appear to be not worth the effort for one reason or another.
Matthew Szatmary
0
0
Senior Video Encoding Engineer at Twitch.TV
Qt 5.1 has(preliminary)support for iOS and android
John Wallace
2
0
John Wallace Entrepreneur
President at Apps Incorporated
Don't take this approach. I invested a HUGE amount of time and money with a Java-desktop-based solution. I also looked at other approached (Air and Qt). When it was all said and done I would have invested a fraction of the money if I had taken a platform-native approach. The problem wasn't the underlying code. That part was beautiful. The problem is that each platform at the UI level has idiomatic differences. Macs and Windows look and feel different. Android and iOS look and feel different. We spent so much time making the code feel right for the platform (which our users absolutely demanded) that it would have been far cheaper for us to write the code for each platform. The other benefit of being platform native is that you can get to market faster, albeit without the full spectrum of targets. There are problems with the write-many-run-many approach, sure. But don't be seduced with the allure of finding a write-once-run-many solution. Biggest mistake I ever made. GIve me a shout. I'd be happy to let you know what worked and what didn't work for us. [removed to protect privacy]; [removed to protect privacy]
Alexander Laszlo Ross
2
0
Alexander Laszlo Ross Entrepreneur • Advisor
Head of Business Development at Verifide
I feel cross-platform stuff is currently a mess- no matter which path.I just spent a lot of time working on tools for all of the above plus we needed a SaaS/web version. We used AIR and Flash but be prepared to hear the "Flash is dead" phrase from the peanut gallery, including investors. You didn't mention the need for a web-based version so that makes Qt a possibility for you.

I agree with John that cross-platform UIs can cause problems but I don't think this is always the case. Some applications do lend themself to more standard native UIs but others do well with a custom look across platforms. Spotify uses embedded Chromium for cross-platform and web apps. This is an option too but a not a mature and proven path. Which means the safest assumption is there will be some engineering headaches in doing so.

Personally, I couldn't fathom actually trying to manage seperate code bases for: Windows, OSX, iOS, and Android. I can't help but think you'd spend more time coordinating than developing new features.

Last question- do you really need to be cross-platform? Sometimes it is better to nail it on one platform rather than spread resources. In my case, unfortunately, this was not an option.

In summary, I felt working across platforms (mobile and desktop) was a 'damned if you do, damned if you don't process.' Compared to the web development many of us are used to- writing one server version and tweaking for different browsers- it really seemed a pain to me.

Join FounderDating to participate in the discussion
Nothing gets posted to LinkedIn and your information will not be shared.

Just a few more details please.

DO: Start a discussion, share a resource, or ask a question related to entrepreneurship.
DON'T: Post about prohibited topics such as recruiting, cofounder wanted, check out my product
or feedback on the FD site (you can send this to us directly info@founderdating.com).
See the Community Code of Conduct for more details.

Title

Give your question or discussion topic a great title, make it catchy and succinct.

Details

Make sure what you're about to say is specific and relevant - you'll get better responses.

Topics

Tag your discussion so you get more relevant responses.

Question goes here

1,300 Followers

  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
Know someone who should answer this question? Enter their email below
Stay current and follow these discussion topics?