View Development Paradigm - which one?

[Former Member]

Hi All,

I suspect this has been discussed before but I can't see the wood for the trees at the moment...  I'm taking my first proper steps in SAPUI5 development in anger and wondered if there is a preferred view type?  Is there a pro's/con's document or some sort of decision tree to help decide which paradigm to go for?

If it helps, I'm more used to working with JavaScript and HTML so would naturally tend towards one of those.  JS looks especially similar to how many other SAP UI technology has worked in the past in my mind so looks to be easier for me to get into but am happy to be guided...

Thanks,

Gareth.

[Former Member · Accepted solution]

Thanks everyone for your thoughts and comments.

Most answers pretty much summed up where I'd got to in my own head, and that a lot of the choice was down to personal preference.  However, I quite like ' point about XML views being the paradigm of choice for Fiori and I guess ultimately, it was this sort of guidance I was hoping for.

After only a short amount of meddling with SAPUI5 I'm realising one of it's key strengths - flexibility - is also a challenge as it makes the decision on "best approach" more difficult.  Maybe I'm spending too much time worrying about how best to structure an application and instead should just crack on and get coding?!

I'm now lost in a world of confusion around Application.js files and other such stuff - my OCD about the "best" way to build something is stopping me getting going

Gareth.

[qmacro · Accepted solution]

Be warned that the Application(.js)-based approach is being deprecated in favour of the Component based approach. Have a look at the quick run-through of a typical Fiori app here to get a feel for it.

[Former Member · Accepted solution]

DJ - thanks very much.  I've just learnt more in ~11mins of watching that video than 2 days of random hacking