package name & versionCode

[IzzySoft]

Did you change the packageName with the newest release? Until the one before, it was de.FhemNative.FhemNative. The APK attached to the latest release identifies as de.fhemnative.app. Is that intentional? Android will consider that a completely different app, so using that to update a previous version is not possible.

Speaking of which: versionCode is 1, indicating an initial release. This might fit the bill of "new app with new packageName", but for updates it must of course be incremented.

Please let me know soon so I know how to deal with your app's listing in my repo, where it resides for almost 2 years now. Thanks!

[Syrex-o]

Hey,
The package name is completely correct. The switch to a capacitor, some large background changes and the coming process to publish the apps to the stores, resulted in the new name.

The version code is not intended. Actually the app version code is 3.0. The package.json version in the new "FhemNative Mobile" is 0.0.0.

I don't know, where your version code is coming from?

[IzzySoft]

Wow, that was really fast – thanks! Then I'll establish the app with the new package name and add a deprecation note to the old one, pointing to its successor.

versionCode is an integer – what you describe is versionName. From aapt d badging on the new APK:

package: name='de.fhemnative.app' versionCode='1' versionName='3.0'

As it's the first release with this package name, it's technically OK and practically no issue – there is no previous version to update (at least not for the "normal users"). As you can always increase (but never decrease) versionCode, you can decide on that with the next release (how much to increase, that is).

Now we just need to decide what metadata I can copy from the original version. There's no Fastlane, no screenshots, no PlayStore listing I can check for the new one, so I'll just copy over the "old one" for now. The "old one" got a deprecation mark, pointing to its successor, and will be removed at some point in the future (just let me know when you want it gone). If you have some newer screenshots, or updates to the description, be welcome to pass that to me. I could then also provide you with some initial Fastlane structures so you have that in your hands (my repo updater would pull that along with the APK – and you can also use Fastlane to ship to other stores, like e.g. Google).

[Syrex-o]

Ok,
Got that fixed.

Coming versions will be signed the following way:

• versionMajor = 3
• versionMinor = 0
• versionPatch = 1

This results in:
versionCode versionMajor * 10000 + versionMinor * 1000 + versionPatch * 100
and
versionName "${versionMajor}.${versionMinor}.${versionPatch}"

This should be appropriate.

I don´t know how we should proceed, when the App is shipped to the stores? The community agreed on a one time price of 5€.

Now we just need to decide what metadata I can copy from the original version. There's no Fastlane, no screenshots, no PlayStore listing I can check for the new one, so I'll just copy over the "old one" for now.

FhemNative.de is launching as soon as the firmation is done. There will be lots of images and live exmaples. Not 100% sure if you mean this?

[IzzySoft]

This should be appropriate.

This is one of the common schemes used in versioning, yes – so it sounds good! If you plan to have your app on F-Droid.org, versionCode and versionName must have literal values for auto-update to work, though (no such issue with my repo).

I don´t know how we should proceed, when the App is shipped to the stores?

Oops…

There will be lots of images and live exmaples. Not 100% sure if you mean this?

Not exactly. Did you check the link to my Fastlane Cheat Sheet? Basically, it's a kind of standardized way to provide summary, description, screenshots and more. The format is accepted by several stores – fastlane supply can ship to Play Store, F-Droid.org and my repo simply pull it along with new releases. What's in there is fully under your control, which makes it easy to keep it updated for all places supporting this. All done via simple text and graphic files. I could provide you with prepared summary + description for German and English as used in my repo to get you started, and you could build on that. If you want it, that is.

[Syrex-o]

I don´t really know what your

Opps...

means?

[IzzySoft]

Well, if you follow the link it maybe explains itself? It already shipped to my repo when I read that sentence, so I somehow had the feeling of having produced facts in advance of your plans…

[Syrex-o]

I know your Repo and I very much like the fact that FhemNative is available in an alternative store. So no problem that RC.1 and RC.2 are in your repo. There will be a point in the near future, when the releases page here will only contain Windows and MacOS. This marks the start of "Store Releases".

My point was more about the future.
Do you have any stats for FhemNative (Downloads/Engagement) from your Repo?

Due to the fact, that iOS support is coming and FhemNative will be part of an "UG", the stores with little one time fees are needed. Everything is already discussed with FHEM and the FhemNative community. "Just informative for you".

[IzzySoft]

no problem that RC.1 and RC.2 are in your repo.

Ugh – thanks!

There will be a point in the near future, when the releases page here will only contain Windows and MacOS. This marks the start of "Store Releases".

And marks the point were I can no longer update it in my repo – as that's where I pull the APKs from. So at that point we need to know how to proceed with that: unlisting from my repo, or find an alternative way of getting the APKs (see here for options).

Do you have any stats for FhemNative (Downloads/Engagement) from your Repo?

Not really, I keep no stats (no analytics or such). I can only grep the logs – which states 70 downloads since July 4th from the repo, plus 39 via the repo browser integrated with my Android site – so around 100 downloads a week. No idea how many of those were first-timers, updates, or other details.

stores with little one time fees are needed.

I cannot offer that, neither does F-Droid. All we offer is donation links – and you can have several of them, like OpenCollective, Liberapay, Flattr, Bitcoin, Litecoin and a "general link" simultaneously. Currently, your app is set up with your Paypal link as "general link" – if you have a donation page listing up all options, that could be used instead.

[Syrex-o]

Sorry for the late response. Was on vacation.

Oh, that's quite a lot engagement. Thanks for the number.
I definitely like the fact, that FhemNative ist open source and available in alternative stores. What do you think of an exclusive "FhemNative Free" version, that is continuously shipped to GitHub as APK?
In order to get this working, FhemNative free would need at least one "ad Banner".
Please let me know what you think.

[IzzySoft]

Sorry for the late response. Was on vacation.

Hopefully a restful one you enjoyed – and not some "work vacation" 😄 Welcome back!

Oh, that's quite a lot engagement. Thanks for the number.

Gladly! And I was a bit surprised, too. I surely expected 2-digit downloads – but the two together are 3-digits, wow!

I definitely like the fact, that FhemNative ist open source and available in alternative stores. What do you think of an exclusive "FhemNative Free" version, that is continuously shipped to GitHub as APK?

That'd be definitely welcome!

In order to get this working, FhemNative free would need at least one "ad Banner".

As long as that doesn't mean some proprietary component, I'd say that's OK. An alternative variant would be leaving out a "boon" which could be retrieved by payment – like it's done e.g. by Netguard (which is available via F-Droid, so definitely no proprietary component inside). When that "boon-feature" is accessed in the free version, instead of invoking it there's be a hint on how to "set it free" (e.g. a link to a page with payment info and details, plus a short explanation on "why").

[Syrex-o]

Hopefully a restful one you enjoyed – and not some "work vacation" 😄 Welcome back!

Haha thanks - Kind of relaxing 😉. Will be working on FhemNative more intense again from August on. The company formation will also be handled in August (finally😂).

As long as that doesn't mean some proprietary component, I'd say that's OK.

What do you mean by that? I would prefer to use Google AdMobs. Any thoughts ?

An alternative variant would be leaving out a "boon" which could be retrieved by payment

Not a giant fan of this. FhemNative should always be "full featured". I think this often frustrates users, especially in those type of applications.

[IzzySoft]

What do you mean by that? I would prefer to use Google AdMobs. Any thoughts ?

Yepp, but you won't like them: that's proprietary, and a show-stopper for F-Droid. Like all ad libraries I know. Plus privacy proponents would choke at that ("GAFAM") and be scared away. So better not. That's why I brought up the "alternative variant" – you could pick some non-essential "nice-to-have", just as motivation. Guess most users would be willing to donate but often forget (or think you don't really care), so that would serve as a reminder.

As to the frowning, here's some background. Though that's only the tip of the iceberg.

[Syrex-o]

Yepp, but you won't like them: that's proprietary, and a show-stopper for F-Droid. Like all ad libraries I know. Plus privacy proponents would choke at that ("GAFAM") and be scared away. So better not.

Ok, that is limiting me quite hard. But guess there are benefits on both sides.
What about having a free version with a limited amount of components/rooms? I would love to implement something as: "Watch short ad and create additional components". But if thats a total showstopper, I don´t see other solutions. But I´m totally open to other suggestions.

Guess most users would be willing to donate but often forget (or think you don't really care), so that would serve as a reminder.

As FhemNative will be part of an actual company (in founding process), donations are not very suitable. I already cleared the MoneyPool.

P.s. Sorry for the late response.

[IzzySoft]

Ok, that is limiting me quite hard. But guess there are benefits on both sides.

Well, every medal has two sides. But nothing is keeping you from adding your own ad component (guess why there's an Ads AntiFeature at F-Droid, there must be some "non-proprietary" way for this – and indeed we have several apps using such).

What about having a free version with a limited amount of components/rooms?

That's an approach taken by several apps, and fully acceptable. The "bonus features" could then be unlocked via some key to be acquired, for example (look at e.g. NetGuard or FairEmail which handle it that way).

As FhemNative will be part of an actual company (in founding process), donations are not very suitable.

Eh, no. Unless it's a non-profit company – which I doubt being your goal 🤣 So the above would be possible approaches then.