Are there anyone that use project management apps? What is a good one? I use SG Project Pro on my iPad, and pretty much this is the only app still tying me to my iPad. I'd love to find something similar on the Android side so I can truly be Apple free.
Basically, SG Project Pro has an intuitive interface, multiple ongoin projects, linking with MS Project, Very good reporting features, Gantt timeline, action list, batch email to all contractors, and risk management. If there is one like that for Android, I'd be ecstatic.
It doesn't need to be free. SG costs 40 bucks and is worth every penny and more. I don't mind spending the money for a well made one, keyword being well made, at least on par with SG Project Pro.
There are only two apps for that and only one allows editing. Android tablets suck when it comes to productivity. Search the market for Ms project. Can't link from tapatalk easily.
Sent with transforming Android technology.
Project Management App
Oh.Y.Not said:
Are there anyone that use project management apps? What is a good one? I use SG Project Pro on my iPad, and pretty much this is the only app still tying me to my iPad. I'd love to find something similar on the Android side so I can truly be Apple free.
Basically, SG Project Pro has an intuitive interface, multiple ongoin projects, linking with MS Project, Very good reporting features, Gantt timeline, action list, batch email to all contractors, and risk management. If there is one like that for Android, I'd be ecstatic.
It doesn't need to be free. SG costs 40 bucks and is worth every penny and more. I don't mind spending the money for a well made one, keyword being well made, at least on par with SG Project Pro.
Click to expand...
Click to collapse
Hi, I have used Project Planning Pro, available on iPad, Android and Windows and found it to be the only app that offers quality features at a minimal price ($20). The availability of this app on multiple platforms make it useful for users utilizing different platforms.
I am particularly fond of its ability to open MPP files in XML format within the app. Once the file is opened, it can be read or edited as per needs. It also allows import of files via Dropbox and mail.
Related
Hi,
new to the forum here, but I've been lurking for a while. I hope I'm posting this in the right section...
I'd like to bring devs' attention to an app developed for iOS, OS X and Android called iRealb. It's meant for musicians to use as a practice tool, chord chart library and composing tool. You basically enter a bunch of chords and it automatically generates a playback track in different styles using semi-realistic bass/drums/piano/guitar.
It seems the developers aren't interested in making a Window phone or desktop version of their app, claiming they just "wouldn't have the time" but from various posts in their forums it seems they would consider collaborating with someone.
I think there's a lot of potential for revenue if this app was ported to WP, and especially W8. The only real competitor for this app on the desktop is Band In A Box - PG Music were the first to come up with the concept - but it's butt ugly and way more expensive. It also has more features, like soloists and audio tracks (as opposed to synth) but most of them come as paying add-ons. As a comparison, the cheapest version of BIAB is $130 while iRealb for is $7.99 for iOS, $10.99 for Android and $19.99 for OS X. Making a similar app from scratch would also be an option but it would probably be way more work than porting both the mobile and desktop versions that are already developed. Anyways, obviously my opinion is probably biased as I'd really like to be able to use this app on both my WP and desktop.
Thanks for reading and sorry about providing no link, it seems I don't have enough posts to link to content outside the forum.
Okay, this will be more of a rant.
So on non-android linux there are about 10000000000 useful, top-notch, cutting-edge, great, perfect and all round ass-kicking programs around. You can download all sorts of crazy super cool stuff for free because the free software and open source software community is producing awesome things. In many cases the open source and/or free alternatives are much better than the proprietary ones. I can't really think of a need when I couldn't find a really great open source library or full program to do the job.
But with android it's different. On Google Play there is all sorts of crap, feature-less and expensive stuff, the free version of a program is typically unmitigated ape****, the reviews/ratings/etc are useless. There are some exceptions like the terminal emulator, or sl4a, but for gods sake where is the geek community here? With fedora/ubuntu/debian/arch/etc we didn't need a centralized crap store and fancy useless ratings/reviews/etc and everything was still wonderful and you could actually get things done. In android, not so. There isn't a single fully functional open source and free GUI for browsing webdav or files over scp, but that's just the latest frustration of mine. Whenever I think of a program I'd love to just search for, download, install and use in 5 minutes which is the norm in a usual linux environment I know in advance that 8 out of 10 cases it won't be that easy on android.
And so where did all the non-free stuff get us? Now everyone is offering crap for money, all ****ty stores incorporate this supposedly to create incentives for developers to innovate because you know, without money there is no innovation at all on the face of this Earth but let's face it, when things were open source and/or free things worked (i.e. ordinary linux) but now they don't. Seems like the model is just not working.
Why can't I have the same linux experience on my bloody phone as the one I have on my laptop and desktop?
Who screwed this up and when?
Can we still fix it?
Android was meant for consumers as an option to the iPhone. Not for people to get all techy with it.
And most Android users ARE simply consumers who want a smartphone with "app and games," internet browser, texting, email, facebook, and calling
Ask that same consumer about computers, and I can almost guarantee they think its a Mac and PC (in which they mean Windows) battle. Mention Linux, and they'll look at you puzzled.
Sent from my DROID2 using xda premium
Android isn't totally open source. Still better than apple though.
Sent from my Samsung Galaxy Exhibit 4G running Cyanogen Mod 9.
We are not limited to the Play "crap store" since we can sideload .apk files from alternative stores, or from wherever you get them. Also, I wouldn't call the Play store's reviews "useless;" I actually think they're generally helpful, and certainly better than the reviews in the Ubuntu "store."
Also, remember that Google built it's empire on selling advertising, and selling access to analytical data. The general *nix community doesn't have that. That's the difference between "open source" & "free."
-- Sent from my TouchPad using Communities
Yes, we don't need to use google play, but how many software packages are out there for android outside of google play? Not many. Certainly orders of magnitude less than ordinary free software available for desktop linux.
I see the fact that google invented android in order to make money, sell ads, etc. That's clear, so I agree with a commenter that android is not really techy from the get go. But why isn't there an ordinary linux based phone? I hear meego is dying, but why is that? Or why isn't there an alternative to meego which follows the ordinary linux philosophy, being community driven, perhaps with a corporate sponsor like redhat or canonical?
The same path that worked for the desktop is currently does not seem to be there for the phone although I'd think it's just another computing platform, not much different after all.
I honestly think we will never see a true open source phone. There are carriers that have to carry that phone and they want users to be able to have the latest and greatest when it comes to their phones and they want it to be easy for them to use. Android & IPhone both offer that experience a full functional Open Source phone would not offer that experience, you would have to build the source from scratch and flash it to your phone which wouldn't be fun for most users. Plus android has the full source code available here http://source.android.com/source/index.html which is how you get Cyanogenmod builds most of the time, they use google source to build that ROM.
tortib said:
I honestly think we will never see a true open source phone.
Click to expand...
Click to collapse
The Openmoko-Project has grown very far,
the FreeRunner is pretty cool:
> www.openmoko.org
not only the software development is open, you can already even print your case at home if you own a 3D-printer:
> projects.goldelico.com/p/gta04-main/page/CaseDesign/
Hello,
I've been doing some research on the many, many different routes I can go with Android development, and I'm hoping someone might be able to help narrow down my choice. My experience is currently web related, PHP/HTML/CSS, with knowledge of intermediate Javascript, etc.
I'd like to create a very similar game to Football Manager, but less ambitious. For those that aren't aware, it's a simulation game where you're the manager of a soccer team.
My ambition is to keep it very simple, dumbed down. No need to watch the games, pretty much all text with simple graphics for some things.
My issue is, trying to find a place to start. There's literally a lot of different routes, and I'm overwhelmed. Do I use HTML5? Java? One of the programs like Unity, Construct? PhoneGap?
For my specific game, and idea, what would be your best suggestion on what to use?
Thanks in advance.
you can try CocoonJS. it's easy.
It's html5 fraemwork.
CocoonJS is a technology that helps HTML5 developers publish their web-based games and apps in the most important mobile and web stores with no code changes and with all the advantages of native development.
Using CocoonJS, a single code base is enough to publish a game or app natively on more than 10 stores. Best of all, with no installations thanks to our cloud-based platform.
HTML5 is finally ready for cross-platform app and game development!
Learn more: http://ludei.com
But now it's in open beta.
All free, but all Extension only for premium users.
Premium account granted for free, if you have nice idia/project.
The answer is "it depends"
A couple of questions...
1. Will it only be for Android? or are you also planning to push it to iPhone?
2. Will the interface be more like a app (eg. gmail, calendar, utility apps) or more like a game (immersive, completely different interface) ?
3. Will there be a lot of interaction? or mainly consuming information?
pyko said:
The answer is "it depends"
A couple of questions...
1. Will it only be for Android? or are you also planning to push it to iPhone?
2. Will the interface be more like a app (eg. gmail, calendar, utility apps) or more like a game (immersive, completely different interface) ?
3. Will there be a lot of interaction? or mainly consuming information?
Click to expand...
Click to collapse
1. Android to start, possibility of iPhone in the future.
2. Straight forward, more like an app, nothing too pretty, more statistical.
3. Mainly consuming information, lots of behind the scenes work.
In that case, I would say go for a mobile friendly web-based app, as opposed to a native app. So this would mean HTML/CSS/JavaScript.
Reasons are:
You want to eventually be on both Android and iPhone. Since you're app is more "app like" if you go native, you'll essentially have to write 2 separate apps to have good user experience (Android and iPhone have vastly different experience guidelines). WIth a mobile-friendly website, you'll satisfy both with one code base
You've already got experience in HTML/CSS/Javascript - definitely a big win!
Since your app will mainly be information consumption, it sounds suitable for a website.
When done correctly, a mobile-friendly website can still be a great experience to use
A couple of things to be aware of...
Don't try and imitate the native UI on the mobile-friendly website. It is a website, not a native app! Users are fine if it doesn't behave like a native app (afterall, they would've just reached your site via the browser). In fact, if you make the website behave sorta like a native app, it might confuse users more. Best direction is to have a good, solid ,easy to use and understand UI. (Be wary of the Uncanny Valley)
Unlike laptops/desktops, mobiles generally are less powerful, so you'll need/want to optimise performance. Make sure the website runs fast & smoothly (ie. optimise resource downloading, minimise/optimise javascript animations etc). Be aware that most phones have a 'click delay' (to detect swipes/drags etc) so you'll want to use something like fastclick to eliminate this.
Remember that on a mobile device your user will be using their fingers (and not a mouse) to click/interact with your website. So make sure tap targets are nice and large.
Finally .... test on a real device! Chrome dev tools etc to simulate phone screens is great for dev, but actually using your website on a mobile will reveal many design decisions that might need to change.
This might sound like a lot to think about, but I think given what you've said about your idea, in the long run, it will be more time efficient. (there is probably a equally long list of things to think about when developing a native app!)
Good luck with your idea
pyko said:
In that case, I would say go for a mobile friendly web-based app, as opposed to a native app. So this would mean HTML/CSS/JavaScript.
Reasons are:
You want to eventually be on both Android and iPhone. Since you're app is more "app like" if you go native, you'll essentially have to write 2 separate apps to have good user experience (Android and iPhone have vastly different experience guidelines). WIth a mobile-friendly website, you'll satisfy both with one code base
You've already got experience in HTML/CSS/Javascript - definitely a big win!
Since your app will mainly be information consumption, it sounds suitable for a website.
When done correctly, a mobile-friendly website can still be a great experience to use
A couple of things to be aware of...
Don't try and imitate the native UI on the mobile-friendly website. It is a website, not a native app! Users are fine if it doesn't behave like a native app (afterall, they would've just reached your site via the browser). In fact, if you make the website behave sorta like a native app, it might confuse users more. Best direction is to have a good, solid ,easy to use and understand UI. (Be wary of the Uncanny Valley)
Unlike laptops/desktops, mobiles generally are less powerful, so you'll need/want to optimise performance. Make sure the website runs fast & smoothly (ie. optimise resource downloading, minimise/optimise javascript animations etc). Be aware that most phones have a 'click delay' (to detect swipes/drags etc) so you'll want to use something like fastclick to eliminate this.
Remember that on a mobile device your user will be using their fingers (and not a mouse) to click/interact with your website. So make sure tap targets are nice and large.
Finally .... test on a real device! Chrome dev tools etc to simulate phone screens is great for dev, but actually using your website on a mobile will reveal many design decisions that might need to change.
This might sound like a lot to think about, but I think given what you've said about your idea, in the long run, it will be more time efficient. (there is probably a equally long list of things to think about when developing a native app!)
Good luck with your idea
Click to expand...
Click to collapse
Thank you very much for your help, I appreciate all the information. One last question on my end.
I'm assuming the development tools would be the same as a usual website (ie. In my case, Dreamweaver?). If you're familiar with Game Dev Tycoon, would a layout /similar style of interaction game b, e capable using only Dreamweaver, or is something else needed?
No worries, more than happy to help
I would actually suggest not using Dreamweaver as for the mobile website, you'll really want to be as lean and minimal as possible. From what I recall, Dreamweaver can add quite a bit of 'cruft' to your code.
I would suggest a standard text editor (recommend: http://www.sublimetext.com/) as that would allow you to have complete control over your code, what you include/exclude, what goes where etc. The mobile site will require that extra attention as you really want to make sure it runs smoothly on the mobile.
In terms of quick dev iteration (making sure the site looks correct) you can use the chrome developer tools (https://developers.google.com/chrome-developer-tools/) which allows you to fake the user agent/screen size etc on your browser. Though nothing beats occasional testing on a real device - just to make sure you're on the right track.
Had a look at Game Dev Tycoon and I would say for something as involved as that (lots of interaction, animations etc) it's better to go down the native route.
pyko said:
No worries, more than happy to help
I would actually suggest not using Dreamweaver as for the mobile website, you'll really want to be as lean and minimal as possible. From what I recall, Dreamweaver can add quite a bit of 'cruft' to your code.
I would suggest a standard text editor (recommend: http://www.sublimetext.com/) as that would allow you to have complete control over your code, what you include/exclude, what goes where etc. The mobile site will require that extra attention as you really want to make sure it runs smoothly on the mobile.
In terms of quick dev iteration (making sure the site looks correct) you can use the chrome developer tools (https://developers.google.com/chrome-developer-tools/) which allows you to fake the user agent/screen size etc on your browser. Though nothing beats occasional testing on a real device - just to make sure you're on the right track.
Had a look at Game Dev Tycoon and I would say for something as involved as that (lots of interaction, animations etc) it's better to go down the native route.
Click to expand...
Click to collapse
Thank you again. I appreciate all your help.
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
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.