HN user

moritzmoritz21

6 karma
Posts3
Comments20
View on HN

I am currently working on a small side-project focused on React Native apps to manage their version update and maintenance mode. - https://appcockpit.dev

Right now I am getting my first users and already getting great feedback. Many things on the roadmap.

Always eager to learn more about others pain points when it comes to React Native/mobile development. Let me know what you think!

Looks very interesting, going to give it a go adding guis to some existing cli python toys I've built

and your python cli you want as bundled iOS/Android app? I don't buy it.

But anyway everyone has different problems and if this 1000 framework is solving this, congrats :clap:

Sorry to play the bad boy here.

But we have 2020 these 2 Apps (Android and iOS) are looking like websites from the 90s.

I don't get the point why everyone wants to add a framework to write one codebase and deploy on many platforms.

There are great working frameworks out here why we need the 100 framework doing this?

That sounds so great! You were working in an area where computers had black-green terminals, you saw when people were afraid what will happen if the date changes to 2000 :scream:, you saw the Sony Ericsson handy area, smartphones, tables, wearables and now ML! Exciting man and I want to be able to write here in ~40 years.

Congrats to all what you have achieved! :clap:

To dive in the questions ...

Another thing I'd like to see is some sort of version control and changelog/commit message functionality. Having access to the current events and their context is one thing. Having context around what changed and why is another layer of value that is critical for teams that may not be closely interacting on making these changes.

versioning I am currently working on. So you are able to go back in history and see what events were tracked for each version.

I'd echo your suggestion about actual events. These should probably be funnel-related events and not random product activity.

Can you give me an example here? :) I am an engineer and may not see the "other side" of the events.

I want to provide a platform where the tech team/product manager can organise all the events.

Where the tracking is tacking place is not determinate. It can be Amplitude, Google Analytics, Firebase, ..

So yeah you can somehow call it "schema tool" to build a template for your tracking.

Well at least in my previous companies and the current one we always had one big excel/google/n sheet where all events were organised with their name e.g. "Profile loaded" and the associated parameters "user name", "user id".

And there were sometimes big discussions and unclear documentary about the events.

Hey everyone!

I worked the last weeks on a problem I wanted to solve and came up building this (so far) small tool.

In the backlog are quite a few features I want to add to it.

The idea behind moanalytics.com is to replace the well-known google sheet companies are using to organise their tracking events for a product. Tracking events always have some parameters which are written down in these sheets.

Additionally I am working as a software engineer and there is always a manual process to copy&paste the events from the sheet in the actual product. This is solved now since I added an export for the events.

Please try it out and I am happy about any feedback :)