Export functionality limitations on iPadOS

[Edgar34869157o9je]

Not sure if this should be labeled as an idea or a discussion but it certainly needs fixing. 

When on Window's or Mac, I get full fledge options and features when it comes to exporting a large batch of photos. One example, is the nomenclature. I'm able to define how to name all the photos I export rather than the photos just taking on the same name that the camera labeled them as when I took the picture. 

The biggest issue I have is that on my windows, it asks me to select my options (file type, watermark location, metadata, etc), then immediately asks for the location in which the photos will be exported to. After choosing the folder location, the export begins one rendering and exporting each photo at a time. As the photos complete, I see them individually populate on my computers' desired location. This does not occur on my iPad and it's the biggest drawback when it comes to making the switch from a computer to the iPad. The iPad forces me to wait for all the rendering to complete, which means it's taking up space somewhere on my iPad, also means that I have to sit and wait for however long the batch of photos will take, the bigger the batch the longer I have to periodically check, and finally asks me to select a file location. Sometimes I'm unable to get to this point as it'll get stuck if the batch is too big or just freeze up on me. Assuming it even gets to this point, I have to then select the folder location and either it will error out or have the same freeze or stuck spinning situation on a random photo. It's very inefficient and buggy. 

Can we please bring the same procedure that occurs on PC/Mac and bring that to the iPad? This way it can render one photo, export it, and place it in it's location, giving the app the opportunity to clear that cached data and start again with the next photo. 

I do understand that the inner workings are more than likely much more complex than the way I simplified it. However, I can't help but feel that the current procedure has some very severe inefficiencies on both time and space complexities. 

[JohanElzenga]

I think it simply boils down to the fact that an iPad is not a flat desktop computer. If you want all the features that a desktop computer has, then use a desktop computer. The possibilities in iPadOS have improved over the years and will no doubt improve further, but it is still a tablet, not a full fledged computer.

[AlexJz]

I would say this is highly debatable.

iPad have the same M1/M2/M3 processors as any of the MacBook, on par on the performance front, and potentially faster than a lot of computers used by people today.

So it's not a performance issue.

Just look at what Blackmagic did with DaVinci Resolve on iPad, on how many of the functionnalities are the same.

The main issue between a tablet and computer remains the UI adaptation for touch.

While I can understand it could take time, to convert some elements to touch, this can't be the case for a simple dialog screen like we are talking here.

Apart from this, I'm really not sure what makes a laptop more "fully fledged"