DEV Community: shyam manek

I'm looking for 10 app teams to try Appavio-AppOps for free. 🙌

shyam manek — Tue, 06 Oct 2026 10:21:50 +0000

I'm looking for 10 app teams to try Appavio-AppOps for free. 🙌

Who it's for:

Indie developers and small teams shipping iOS and/or Android apps
Agencies managing apps for multiple clients
Anyone who's been burned by outdated store listings or missing assets

What you get:

Free early access
Direct setup help from me
A say in what I build next

What I ask:

Honest feedback after you've used it

Interested? Comment "Appavio-AppOps" or send me a DM, and I'll get you set up.

Know someone who ships apps? Tag them 👇

🔗 swtly.co/appavio

mobiledevelopment #appstore #indiehackers #buildinpublic

Story of mobile app release managemant

shyam manek — Tue, 06 Oct 2026 10:20:45 +0000

A few years ago I was [shipping a release / updating an app listing], and found out the iPad screenshots were missing. Again.

I'm a mobile developer ([React Native / Swift]), and I kept running into the same things:

→ Hunting for the latest screenshots
→ Copy-pasting store descriptions between locales
→ Digging through Slack to remember what changed in the last release

None of it is hard. It's just scattered, and it wastes time that should go into building.

So I'm building AppOps: one place to manage app assets, store copy, locales, and release history.

Less release chaos. More time building.

It's early, and I'm building it in public. I'll share what I learn along the way.

🔗 swtly.co/appavio

buildinpublic #indiedev #mobiledevelopment #appstore

Shipping the app is the easy part.

shyam manek — Tue, 06 Oct 2026 10:19:43 +0000

The real headaches come after:

📵 Missing tablet screenshots
📝 App Store description still mentions a feature you removed
📁 Assets scattered across Drive, Slack, and someone's laptop
❓ Nobody's sure which version is the current one
🕰️ Release history lives in 5 different places

I've seen this on [every / many] app I've worked on.

Curious: how does your team keep store assets and release info organised?

👇 Tell me what's worked (or what's been a mess).

mobiledevelopment #appstore #iOS #android #reactnative

Appavio AppOps

shyam manek — Thu, 01 Oct 2026 05:10:52 +0000

Shipping an app is easy compared to everything around it.

11 locales.
20 screenshots.
Multiple device sizes.
Different app versions.
Store metadata.
Team access.
Release history.

Soon you have folders, spreadsheets and docs everywhere.

We're building AppOps to bring those boring parts of shipping into one place.

Register → Upload → Localize → Release.

• Versioned assets
• Device-aware screenshots
• Per-locale store copy
• Team roles
• Release history
• Direct-to-storage uploads

Built for developers who ship more than one app.

Try it → Appavio

buildinpublic #indiedev #mobiledev #appdevelopment

I’m building AppOps to make shipping multiple mobile apps less painful

shyam manek — Thu, 01 Oct 2026 04:45:44 +0000

If you maintain more than one mobile app, you probably know how quickly release management becomes messy.

Your source code is in GitHub.

Screenshots are somewhere in Google Drive.

Store descriptions are in a document.

Different language versions are in spreadsheets.

App icons are in folders with names like:

final.png
final-v2.png
final-new.png
final-new-final.png 😅

And then someone asks:

“Which one is the latest version?”

That was one of the reasons I started building AppOps.

What is AppOps?

AppOps is a workspace for managing the operational side of shipping mobile apps.

The goal isn't to replace GitHub, Xcode, Android Studio, App Store Connect or Google Play Console.

Instead, it's meant to sit around those tools and keep the information that gets scattered between them organized.

You can think of it as a central source of truth for your app portfolio.

What I'm working on

📱 App catalogue

Keep all your applications organized in one place instead of maintaining separate spreadsheets.

🖼️ Versioned assets

Manage app icons, screenshots, banners and other store assets with version history.

🌍 Store copy & localization

Keep descriptions and store metadata organized by language/locale.

📐 Device screenshots

Track screenshots for different device types and make it easier to see what is actually ready for release.

👥 Team roles

Give team members appropriate access instead of sharing everything with everyone.

📜 Release history

Keep a record of what changed and when.

Why build another developer tool?

There are already excellent tools for writing and building apps.

GitHub handles source control.

CI/CD platforms handle builds and deployments.

App Store Connect and Google Play Console handle publishing.

But the operational information around those systems often ends up spread across multiple places.

For an indie developer with one app, that's probably manageable.

For someone maintaining 5, 10, 20 or more apps, it becomes much harder.

That's the problem I'm interested in solving.

The bigger idea

I'm thinking about AppOps less as an “asset manager” and more as an operating layer for an app portfolio.

Imagine opening one dashboard and seeing:

My Apps
│
├── App A
│   ├── Versions
│   ├── Screenshots
│   ├── Store Copy
│   ├── Localizations
│   └── Releases
│
├── App B
│   ├── Versions
│   ├── Screenshots
│   ├── Store Copy
│   ├── Localizations
│   └── Releases
│
└── App C
    ├── Versions
    ├── Screenshots
    ├── Store Copy
    ├── Localizations
    └── Releases

The long-term goal is to make the process of taking an app from “ready to ship” → “ready for the stores” much more organized.

I'm still building it

This is an early product, so I'm particularly interested in hearing from developers who maintain multiple mobile apps.

I'd love to know:

How do you currently manage screenshots?
Where do you keep localized store descriptions?
How do you track which assets belong to which version?
Do you use spreadsheets, Notion, Drive, custom tools, or something else?
What part of preparing a release takes more time than it should?

If you manage multiple apps, I'd genuinely like to hear how you handle this today.

Try appavio AppOps

👉 https://swtly.co/appavio

I Tried Cluely and Sidekick for a Week — Here's My Honest Experience

shyam manek — Sat, 27 Jun 2026 08:57:29 +0000

AI assistants have become part of my daily workflow. Whether it's meetings, coding, debugging, or taking notes, I wanted to see which tool actually saved me more time.

Over the past week, I spent time using both Cluely and Sidekick by Squiwo.

Both are impressive products, but I noticed they shine in different areas.

My Workflow

I'm a software developer, so my typical day includes:

Team meetings
Reading documentation
Debugging issues
Writing code
Reviewing pull requests
Taking meeting notes
Researching unfamiliar technologies

I wanted an AI assistant that could stay useful throughout the day—not just during meetings.

Cluely

Cluely performed well for meeting-related tasks.

I liked how quickly it could assist during conversations and help capture information while I was in calls.

If your primary use case is AI assistance during meetings, it's worth trying.

Sidekick

What stood out to me about Sidekick was that it continued to be useful after the meeting ended.

Instead of switching to another AI tool, I could continue asking technical questions, get help understanding code, and work through development tasks in the same workflow.

That reduced the amount of context switching I usually deal with.

What I Liked

Cluely

Good meeting assistance
Helpful during live conversations
Easy to get started

Sidekick

Helpful during meetings
Continued to assist after meetings
Useful for technical questions
Better fit for my developer workflow
Reduced the need to switch between multiple AI tools

Which One Would I Choose?

I don't think there's a single "best" AI assistant for everyone.

If your work mainly revolves around meetings, Cluely may be a good fit.

As a developer, I personally found myself spending more time in Sidekick because it fit better into the rest of my day—not just the meetings.

Being able to continue from meeting notes into coding, debugging, and technical discussions without changing tools made my workflow feel smoother.

Download Sidekick

Final Thoughts

AI assistants are evolving quickly, and competition is great for users.

For my daily development workflow, Sidekick felt more like an AI companion than just a meeting assistant.

I'm interested to see how both products evolve, but based on my experience, Sidekick has become the one I keep open throughout my workday.

Have you tried either of these tools? I'd be interested to hear which one fits your workflow better.

Introduction to OneLink in AppsFlyer in React Native

shyam manek — Mon, 07 Apr 2025 09:04:40 +0000

What is OneLink?
OneLink is a feature provided by AppsFlyer that simplifies the deep linking process. It creates a single link that can redirect users based on whether they have the app installed or not. If the app is installed, it opens directly; if not, it redirects to the appropriate app store or a web landing page.

Prerequisites
Ensure you have the AppsFlyer SDK integrated into your React Native project.
Use the latest version of the AppsFlyer React Native plugin.

Installation
To install the AppsFlyer SDK for React Native, run:

npm install react-native-appsflyer

cd ios 
pod install

//add this to the pod file
pod 'react-native-appsflyer', :path => '../node_modules/react-native-AppsFlyer'

Implementing Deep Linking

Official Documentation
https://dev.appsflyer.com/hc/docs/react-native-plugin

Example App :
https://github.com/AppsFlyerSDK/appsflyer-expo-sample-app

Step 1: Configure OneLink

Create a OneLink Template: In your AppsFlyer dashboard, navigate to Engage > OneLink Management and create a new OneLink template.

Set Up User Experience: Choose how you want users to interact with your link (e.g., social-to-app, referral-to-app).

Add Deep Linking Settings: Configure deep linking options as needed for your campaign.

Step 2: Handle Incoming Links in React Native
Use the Linking module from React Native to handle incoming deep links. Here’s a basic implementation:

Firebase Dynamic link alternatives in React Native

shyam manek — Thu, 22 Aug 2024 19:46:11 +0000

Deprecated: embed Firebase Dynamic Links is deprecated and should not be adopted in projects that don't already use it. The service will shut down on August 25, 2025.

basic and easy configuration of deeplinking on react native using react-navigation linking

React-Navigation

Documentation reactnavigation.org/docs/deep-linking

For Android

1. Configure App Links in AndroidManifest.xml

To support App Links, you need to configure your AndroidManifest.xml to handle HTTP/HTTPS URLs:

Open AndroidManifest.xml
This file is located at android/app/src/main/AndroidManifest.xml

Add Intent Filters

Update the element to include intent filters that specify the domains your app can handle:


<activity
  android:name=".MainActivity"
  android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
  android:label="@string/app_name"
  android:launchMode="singleTop"
  android:theme="@style/AppTheme">

  <!-- Handle HTTP/HTTPS URLs -->
  <intent-filter>
    <action android:name="android.intent.action.VIEW" />
    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />
    <data android:scheme="https" android:host="www.yourdomain.com" />
  </intent-filter>
</activity>

2. Create an Asset Links File

android requires a file hosted on your domain to verify the relationship between your app and your website. This file is called the assetlinks.json file.

Create the assetlinks.json File
The assetlinks.json file should be created and placed in the
.well-known directory on your web server. The file should be accessible at https://www.yourdomain.com/.well-known/assetlinks.json.

Example content for assetlinks.json:

[
  {
    "relation": ["delegate_permission/common.handle_all_urls"],
    "target": {
      "namespace": "android_app",
      "package_name": "com.yourappname",
      "sha256_cert_fingerprints": [
        "YOUR_CERTIFICATE_FINGERPRINT"
      ]
    }
  }
]

"package_name": Replace with your app’s package name (e.g., com.yourappname).
"sha256_cert_fingerprints": Replace with the SHA-256 fingerprint of your app’s signing certificate.

React Native Lottie Animations

shyam manek — Tue, 07 May 2024 12:23:56 +0000

Lottie is very light weight and easy to use with react native.
also Lottie is good quality and one of the advanced version of gif

Lottie component for React Native (iOS, Android, and Windows)

Lottie is an ecosystem of libraries for parsing Adobe After Effects animations exported as JSON with bodymovin and rendering them natively!

For the first time, designers can create and ship beautiful animations without an engineer painstakingly recreating it by hand.

Lottie npm Package Link

Example

import React, { useEffect, useRef, Animated } from 'react';
import { Animated, Easing } from 'react-native';
import LottieView from 'lottie-react-native';

const AnimatedLottieView = Animated.createAnimatedComponent(LottieView);

export default function ControllingAnimationProgress() {
  const animationProgress = useRef(new Animated.Value(0));

  useEffect(() => {
    Animated.timing(animationProgress.current, {
      toValue: 1,
      duration: 5000,
      easing: Easing.linear,
      useNativeDriver: false,
    }).start();
  }, []);

  return (
    <AnimatedLottieView
      source={require('../path/to/animation.json')}
      progress={animationProgress.current}
    />
  );
}

You can find the full list of props and methods available in our API document. These are the most common ones:

API document For Lottie