Comments

• gusgranite

  May 15

  @FunksMaName Congrats. What’s the app?
• gusgranite

  May 15

  @dendy and congrats to you too!
• dendy

  May 15

  @gusgranite said:
  @dendy and congrats to you too!

  😇 thanks.. i am pretty happy, can’t pretend i am not :-)) it’s just small niche tool which will be probably used just by few people - but it’s first baby step
• FunksMaName

  May 18

  @gusgranite said:
  @FunksMaName Congrats. What’s the app?

  Hey Gus, sorry for tardy reply, been looking away a few days - I'll be ready to announce soon
  It's essentially a super useful networking utility aimed at musicians. Funnily enough it's called FunkyPipe (it has been long before AudioPipeline was on my radar, and complete coincidence!) - it does have AudioLink send support, but I've not bothered asking for permission to create a receiver, I'll happily just recommend people use @dendy 's app for that unless they change their policy... but Link support was added at the last minute, before that (and still I find it better than Ableton link on the same device) it has it's own way of sharing 32bit float audio with no sync overheads between senders and receivers (it does a lot more than just this too, more will be revealed soon.)
• murphlab

  May 18

  I can't speak to the public app store approval right now, but my TestFlight approvals have been relatively zippy.
• jhhl

  May 25

  Hi Folks!

  I've found over the years that a new app gets a lot more scrutiny and takes a longer time to review! Apple reviewers ( when they get around to reviewing the app ) also have a bug bunch of scans to make sure you aren't using useful but undocumented APIs, or have graphics that seem to imply Apple is endorsing your product, things like that. They kicked out Enumero once because I was using the Covid genome as a source of musical notes, and their scripts kept thinking it was trying to cure Covid or something. Idjits. I renamed the patch "Genome" and it went in.

  They have gone through periodic app storage clean-outs too, for instance, dumping zillions of beer, fart , "that's what she said", and flashlight apps that were so popular in the early days. Also, this is by far not the first time robots were used to mass produce apps. For a while bots were just churning through the Project Gutenberg collection, turning each public domain book into an app. Others would use a more or less simple script to make EPK apps for bands. I suspect these zillions of new vibe coded apps will have a lot of overlap, but overlap has never been a reason to kick out an app unless it seems to be plagiarism.

  The real question for these new vibe coding app devs is whether they have any idea of maintaining these apps, because Apple has the tendency to decide a whole well established programming route, or visual style, is being replaced or otherwise deprecated. I also find it kind of quaint and heartwarming that people may think they might be able to live off these apps.

  There can be various levels of AI assistance. A method or class or two , or maybe some UI skinning may not be considered to Ai dependent. Or using AI in the dev process to help run and create testing and be part of continuous integration. Three have been scripts and bots like this for years, just not using large commercial language models.

  There's always the possibility that if there is a lot of trust in vibe coding, the friendly AI will insert hooks into the code to help throw money at the AI's bosses, or use your CPU to mine crypto during your musical rests, or whatever. I can see this being like phishing: it's easy to detect if you know where to look, but what if you don't?
• FunksMaName

  May 26 edited May 26

  I think the threat of hidden crypto mining operations being injected into vibecoded apps by AI seems pretty paranoid...
  However, intentionally created hidden crypto mining operations by nefarious humans on the other hand are much more likely, I'd imagine