Skip to main content

Publishing Insights- A checklist

Wow. What a hell of a few weeks.

 

The app was, admittedly, rudimentary before I finished this last update. Initially, my intent for the app was to select the chords custom to be shuffled - the whole "basic, intermediate, advanced" thing was a workaround because I hadn't the slightest clue how to program that. After some meetings with a Thunkable rep and some surprising thinkwork on my end, the Custom button is finished.

The entire reason I went on this rabbit hole was because I needed to factor in this website. I wasn't able to do so until I had a review and approval from Apple's team, which can take days or a week sometimes. I had already begun the new update when I ran into this roadblock so I needed to finish it entirely before I could re-submit, as I had no way to go back to the initial version. In Thunkable, once you start editing, it's pretty set in stone. No "Undo". 

So it took some weeks, meetings, and a big pause on marketing because people were downloading the app and ads weren't monetizing. Then, on Tuesday, I finally had everything up but I still had a subtle feeling like it wasn't all over yet. 

 Log into Admob, their bot crawled the site, approved! Yes! Thennnnn...... they're like "Oh, btw, you need to re-upload it to be GDPR compliant" so I'm sitting here like "fuckin' hell". 

 Hey. I love that EU users get a choice. That's great and I think America could learn a thing or two. But I wish, when I had bought my Thunkable advanced plan, there was a PDF right as you begin your first project which said 

 

 Things to consider before publishing: 

Apple

- They will reject your screenshots if they don't meet the exact requirements. 

- Editing anything on your app will require a whole new update.

- Put your name in the "Copyright" box, which is located 

- You only need 1 app specific password 

- Your app needs to run through anonymous testing before being placed in the "Review" que.  You add them in under "Testflight" then the + symbol under Groups. They can (and will) reject your app

 

Android 

- Find 12 testers to help your app be approved by the PlayStore. They need to be committed to the 14 day period of testing. 

- You can only test 1 app at a time 

- Do your payment profile verification first. Issues result in app removal 

- Do a closed test! 

- If your app is paid, generate promo codes for testers if you want them to test for free  

 

Admob/General 

- Build a simple website containing an ads.txt so Admob will approve your ads

- After approval, GDPR stuff comes up. You'll need a button to inform users that they can revoke the ads upon opening the app. Button must be visible and easy to access

- There are websites to help you generate screenshots for iPads (I used HotPot AI. Sorry not sorry)

 

That's what I can remember off the top of my head. Thunkable provides a wealth of forums with this knowledge, but I wasn't gonna read a novel before embarking on my idea. Hats off to whoever does that, but it would've taken just as long to prepare for all the roadblocks I would encounter than it did to just face them head on. 

 

Baby's up. Cheers

-B 


 

Comments

Popular posts from this blog

The update to rule them all

 Ok y'all I'm really gonna send it. Firebase. Cloudinary. I was hesitant because I don't know these programs and I don't want to get defaulted into a subscription, but I figure even if I get that many users to justify it, then it's worth a shot. I am holding back on the design updates. I just want everything to send at the same time. All the designs looking the same on all the apps. All the features looping/acting the same. I just want to plop it all out there instead of trickling updates and progress... so yeah things are bound to look messy for the next couple of weeks but I am tinkering away on the back end as much as I can for that final send.  I... am... eexcitttteeeddd!!!! This is so cool! I don't expect it to take off right away, but just to have a new direction to go into with the app. Even though it's unknown waters, it's something new and I'm eager to give this a shot. I really feel good about all of this. It's all been a momsical whim ...

Another Finish line

Wow. I think this next big step is what completes the app. Anything after this will over complicate things. But my last steps are this:  Playlist - a community playlist of chords in the order of songs that you can practice and play.  + you don't need to manually enter something if you can find it + lots of people contributing  Custom - hear the chords before they flash. An option to save decks in an advanced version of the screen + allows personalization at a basic level The only thing is that people will probably prefer the custom saved chords over the community chords, but whatever. The playlist community was really just a workaround for this custom screen thing that I'm just gonna try and ship.  Kind of like when I had just started, with the Styles button. It was a workaround for Playlist, building custom chord decks. But I ended up keeping the feature anyway because it's fun to try.  It's funny how simple my guitar apps look compared to what's coming. This n...

Exhausted

 Alright. Whelp. The update is done. Songs can be saved now. I have to count the days individually and hope that google approves it after 2 weeks and hope my testers actually do the thing. Ughq;eufhjnlfjqwe fiwknf;modwukfnjqvmlierf   as nice as it feels to be doing this app and to feel like I have some sort of direction, not making any money for doing all of this work, hearing back from any recruiters about other types of jobs... one thing at a time I guess. I've been working at this every night for weeks, when she naps, when she sleeps.. it's the only time I get to myself. Now that I'm just done with this update I've got all of this nervous energy built up. I need to rest.