Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Files App vs App Specific Browser

JSMiltonJSMilton
in General App Discussion

Hi everyone,

I'm currently in the process of developing a new app, as well as planning an update for my current one (Poly 2). I'm considering ditching the in app file browser and fully supporting the Files app for both projects, but I'd like to canvas peoples opinions this.

Is the Files app something people are using more and more, or do people prefer an in app broswer? The reason I personally didn't like the Files app is how clunky it all felt, especially previewing samples. Is this something people are willing to live with to get the convenience Files offers?

Thanks for any feedback,

James

Comments

  • JorgeJorge
    edited January 2021

    @JSMilton

    From a developer point of view, I had the same issue with my app.

    I've decided to go for a Document based app that uses the iOS File Browser. Saves on coding work, potential bugs and feels more natural to the user as they don't have to learn a new way of saving/loading.

    I'm very interested in the point of view of a user.

  • 0tolerance4silence0tolerance4silence

    +1 for Files support
    - sooner or later it has to become the main depository imo, with all the necessary features implemented as it grows.
    - split screen, drag & drop are pretty useful workflow enhancements
    - hopefully more enhancements will become available as iOS gets closer to OSX

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • uncledaveuncledave

    @JSMilton I know users like the Files app. They hope it can become like Windows File Explorer, where you can completely modify directory contents, potentially corrupting a program. But from a developer viewpoint, I think the concern is that, if files are referenced by other files, how do you handle their possible removal, even while the app is running. For example, if samples are referenced in a project, what happens if they are renamed or deleted? I see some apps that expose certain folders, while keeping other data private. These are decisions you need to make, needing to maintain data integrity while offering a convenient interface.

  • espiegel123espiegel123

    @JSMilton said:
    Hi everyone,

    I'm currently in the process of developing a new app, as well as planning an update for my current one (Poly 2). I'm considering ditching the in app file browser and fully supporting the Files app for both projects, but I'd like to canvas peoples opinions this.

    Is the Files app something people are using more and more, or do people prefer an in app broswer? The reason I personally didn't like the Files app is how clunky it all felt, especially previewing samples. Is this something people are willing to live with to get the convenience Files offers?

    Thanks for any feedback,

    James

    One advantage of in-app browser is being able to add custom features like auditioning files -- which Auditor does. It supports both in-app filebrowser and Files app.

  • JSMiltonJSMilton

    Thanks for the feedback guys.

    @Jorge All great points and defintely things I've considered, especially saving on code. It seems crazy to develop a whole file browser when there is a ready made one waiting.

    @0tolerance4silence

    • sooner or later it has to become the main depository imo, with all the necessary features implemented as it grows.

    This was also something I was thinking and you're probably right. I suppose I'm just worried about how long it will take and if the Files app is good enough in the meantime.

    @uncledave
    All the issues that arise from the developer viewpoint are secondary for me. It's all about the user. You make good points though and of course I'll keep all that in mind.

    @espiegel123
    Supporting both was something I originally planned for Poly, but that plan went out of the window when I realised you cant share the documents folder with the AU. That meant no sharing user presets and sounds between the standalone app and the AU, which is insane! As far as I'm aware this hasn't changed, so the only way to make it work is to use the Files app browser in the main app and the AU, which is the only way you can access the documents folder from an extension. Basically anything that interacts with file system has to use Apples UI.

    I'm leaning toward going all in on the Files app support at the moment, see if any future comments changes my mind. Thanks again everyone.

  • PoppadocrockPoppadocrock

    @0tolerance4silence said:
    +1 for Files support
    - sooner or later it has to become the main depository imo, with all the necessary features implemented as it grows.
    - split screen, drag & drop are pretty useful workflow enhancements
    - hopefully more enhancements will become available as iOS gets closer to OSX

    Agreed.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025