I was expecting the files report to at least have a list of where it shows the actual human readable files that are used and taken from the asset folder for the build … not this kinda rubbish …Temp/StagingArea/Data/09641b029dfa78843902b548a9de7553 | 272072 | SharedAssets
…what on earth am I meant to do with that crap practically useless. Basically the only useful build report tool for Unity is still the one on the asset store or sifting through effing editorlog.
Meanwhile in UE4 land 
Unity Engine 4? Upgrade you must 
Also I thought that appart from providing an API they would build a simple frontend html file with a table with orderable columns that it’s something they can do in one or two days with libraries like bootstrap.
I know that asset store developers are going to build something on top of this but Unity could provide a simple solution for us.
The files information is output files, not input files. Input files will be coming to a future revision of the API.
UI will also be coming once the API is complete. (No, it is not just “one or two days with libraries like bootstrap”).
I meant one or two days if it’s a html based simple table frontend. I didn’t mean it for a IMGUI interface that its more complex.
With “future” you mean a future beta of 2018.1 or 2018.x?
We’re building an HTML-based UI. It’s much more than one or two days work. (Granted, what we are building is not just a “simple table frontend”).
It will probably be 2018.x, rather than 2018.1, but we’ll see.
Any hints on what kind of features we could expect? Even if it’s not set in stone and still open for change? Would be cool to hear what kind of things you guys have planned instead of “it won’t take one or two days, it’s not simple”. 
And more on point to this thread, what are we supposed to do with the info found in the build report?
What are we supposed to do with this kind of data:
That string I pasted isn’t how it looks from the buildreport … I just took it from the build report file I was making with it from this…
(reportFile.path + " | " + reportFile.size + " | " + reportFile.role);
Anyway disappointing the files section stuff was not what I was expecting, would have thought Unity would release the initial api with at least reporting the actual used input files (not even more advanced info on where they are used or anything)… priorities are a bit up the pole at Unity I guess. I thought 2017 was the year of unfinished api, tools etc going into the editor. My first thing trying in 2018 (only because part of the code caused some scripting errors that needed to fixed in my build tools) and it turns out the new api is practically useless barring a few minor stats.
As far as html build output… I’m fine with a simple html/css only output or that as an option (no doubt it will probably be heavily riddled with javascript and won’t display much of anything useful without it). Personally I would have thought doing an in editor tool for showing build reports with just a simple html output report chucked out with the game build optional. Utilizing something like the bitbucket memoryProfiler gui for visualizing file sizes and grouping usages, and yknow adding some rich functionality for users similar to the asset store tool. Seeing where files are being used more directly from an in editor tool so you can click on them and see where they are in the project and what they are being used in… not some html output that just seems further abstracted from being ‘as useful’ (i’m sure it will still be somewhat useful) …with that output being saved along with the build for archival and later comparison purposes.
So I am disappointed the tool will be html… what happened to using that fancy https://docs.unity3d.com/Manual/TreeViewAPI.html api that got thrown out for some part of build report tool? My only exception to this html output is if you just make some official extra in editor tabs like the asset store tab… that read website/local html files…so a help documention tab already… and build report tool one… and bring that stuff into working in the editor that way aswel as external browser (and add a damn option in the preferences to set the external browser to use for local/external url’s already… I’m annoyed that it lamely tries to use the system default one).