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!

Throughout my career working on native mobile apps, two problems constantly appeared across every company: managing forced updates/version control and managing maintenance mode without a painful backend update or new app release.

I built AppCockpit.dev to solve this. It's a centralized service that gives you a dashboard to control which version is enabled and which requires an update.

Key features:

* Centralized Version Control * Instant Maintenance Mode * Currently focusing on React Native (More SDKs will follow)

I'm already using this in a smaller application and am now looking for feedback from the broader community on the feature set and roadmap. I have many more features planned, but I'm at a point where I need input from others to prioritize.

Let me know what you think about the approach. What is your team's biggest headache with forced updates?

Go check it out: https://appcockpit.dev/

Comments URL: https://news.ycombinator.com/item?id=45516708

Points: 1

# Comments: 0

We launched leaderboard.fun, where the user can create leaderboards and keep track of the scores and ranking. It should be as simple as possible.

You simply create an account and boards with the names of players. You can share the board with a public link. The public boards are updating real time.

If you have any feedback let us know. We have many things planned. The next big thing is a mobile app in the app stores.

Comments URL: https://news.ycombinator.com/item?id=42699224

Points: 1

# Comments: 0

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:

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?

Congrats to all what you have achieved! :clap:

I have one question: What tool did you use to create the docs? => https://docs.cronhub.io/how-to-ping.html#ping-api

So far I have a few users in the "trial" and they are really helping me to push it further.

It is a SAAS to improve the implementation of tracking in your product :) - have a look. Always looking for feedback.

No the product is placed in the development flow before the implementation of the events. It is for organisation of the events you want to track.

I thought about so many names ... checked the domains => taken :D

> 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.

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.

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

I will try to make the product more clear on the landing page :)