Stories by ErenElagz on Medium

Best Feeling as a Entrepreneur. It is First Sale

ErenElagz — Thu, 04 Sep 2025 18:35:13 GMT

Best Feeling as a Entrepreneur. It is First Sale 🚀

3 min read·Sep 4, 2025

I Made My First Sale on Gumroad with a Notion Template 🚀

There’s something magical about earning your first dollar online. For me, that moment just happened — and it came from a Notion template I built called CompanyOS.

Press enter or click to view image in full size

Someone from the US paid $9.70 for it, and while that may sound like a small number, the feeling was priceless. It wasn’t just about the money. It was proof that something I created has real value for someone else.

Why I Built CompanyOS

I’ve been using Notion for a long time, and like many people, I started with simple to-do lists and notes. But as my projects grew, I needed something bigger:

A place to manage tasks and goals
A system for human resources and team structure
A way to organize finance, sales, and expenses
A hub for marketing campaigns, competitor analysis, and customer feedback

Most templates I found were either too simple or too messy. So I decided to create my own, step by step.

That’s how CompanyOS was born: a fully integrated company management system built in Notion.

What’s Inside?

Here’s what you get with CompanyOS:

Home Page: Quick start guide + shortcuts
Tasks & Goals: Track objectives and key results (OKRs)
HR Hub: Employees, meetings, job postings, and feedback
Finance: Sales, expenses, invoices, fundraising, and budget planning
Marketing: Campaigns, calendar, social media, and customer feedback
Analysis: Competitor reviews, SWOT, risk management
Network: Clients, sponsors, partnerships, logistics
Projects: Current projects, R&D, idea tracking
Development: Research, bug tracker, UI/UX system, tech stack

Basically, it’s like a startup operating system, but entirely inside Notion.

The First Sale 💸

I listed CompanyOS on Gumroad with no expectations.

I thought: maybe one day someone will find it useful.

Then one day, a notification popped up:
“You made a sale!”

A person from the US bought my template for $9.70.

I can’t explain how motivating that moment was. It made me realize:

People are willing to pay for digital products.
Even a small idea can find its audience.
The internet truly allows us to build, share, and earn from anywhere.

What’s Next?

This is just the beginning. My goal now is to:

Improve CompanyOS with feedback from users
Add more templates and variations
Share my journey to inspire other creators

If you’ve ever thought about building something online, I encourage you to start small. Your first product doesn’t have to be perfect. Just put it out there — because your first customer is waiting.

👉 You can check out CompanyOS here:

Thanks for reading. If you’ve had your own “first sale” moment, I’d love to hear about it in the comments.

My 8 Year Android Development Story as a student. And Finally I made it!

ErenElagz — Sun, 24 Aug 2025 07:28:44 GMT

My 8 Year Android Development Story as a student. And Finally I made it!

3 min read·Aug 24, 2025

This is the Play Store Link if you want to check.

https://play.google.com/store/apps/details?id=com.leckham

I started Android development at the beginning of high school.

But I bought my first laptop in university. 😅 Yep, you read that right. Because my first “code editor” was my phone.

Back then, there was an app on Android called Sketchware. I spent a long time building projects on it. But it was so limited. you couldn’t fully develop professional projects, writing native modules was almost impossible.

Then Sketchware got removed from the play store, became open source, and other developers improved it. I jumped back in, made some small projects. but nothing “big” ever got finished.

Between preparing for university exams and Google dropping APK support in favor of AAB, my motivation took a hit, and I quit development for a while.

I got into Computer Engineering (my life dream) but still no laptop. For the next 6 months, I survived on lab computers, mostly doing HTML/CSS websites instead of Android.

When I finally bought my laptop, the very first thing I installed wasn’t VS Code. it was Android Studio. But I’d forgotten Java, and I didn’t know any modern frameworks. Honestly, I never have good knowledgement about Java.

Then I learned some JavaScript libraries for web development. I discovered React, and suddenly everything felt easier. That led me to learning React Native, and the idea of cross platform development blew my mind (even though I’m not much of an iOS fan🙃).

I joined competitions, even got some good rankings. Tried a startup in agriculture tech. didn’t work out. I published My Website. Went on Erasmus to Poland (country of Zabbka 🐸). Had an amazing time there, but more importantly, And in Erasmus i was have a project idea: a book reader app.

By then, I had also improved my UI design skills. I followed designers on Twitter and Dribbble, so creating the design was easy. I started coding, thinking it’d take 1 month. It took 2.5 months. I ran into unexpected problems (React Native EPUB support is terrible, PDFs aren’t great either).

But I finished it. I paid $25 for a Google Play developer account.

Uploaded the app… and Google told me I needed 12 testers.

For 14 days I begged friends, family, anyone I could find. Got rejected. Tried again. Another 14 days.

And finally… Google approved it. 🎉

Screenshots, descriptions, and my App Leckham is live.

if you want to check the app:

https://play.google.com/store/apps/details?id=com.leckham

After 8 years, I made my dream come true.

I wanted to share this because maybe you’re reading this with low motivation, maybe it is not true time but trust me, if you keep going, one day it will happen.

Have a good day 😁.

and this image is screenshot from play console, if you want to check and giving advice to me 😁

Press enter or click to view image in full size

Eren.

Short Talk for React Native.

ErenElagz — Wed, 23 Apr 2025 11:06:17 GMT

Short Talk for React Native.

8 min read·Apr 23, 2025

Alright folks, pull up a chair! If you’re looking to build mobile apps that run seamlessly on both iOS and Android without writing everything twice (yeah, the dream!), then you’ve absolutely got to get acquainted with React Native. It’s a game-changer, a time-saver, and frankly, just plain fun to work with.

Think about it: building for mobile used to mean picking a side (iOS with Swift/Objective-C or Android with Kotlin/Java) and then, if you wanted to reach everyone, doing the entire thing over again for the other platform. Ouch! That’s double the code, double the bugs, double the headaches.

React Native swooped in like a superhero with a simple, yet powerful idea: Learn once, write anywhere. It lets you use your JavaScript and React knowledge to build truly native mobile apps. Not hybrid web views wrapped in a shell (though those have their place), but apps that compile to native UI components, giving your users that smooth, performant experience they expect.

Let’s break down why React Native is so cool and lift the hood to see what kind of goodies make up its typical tech stack.

So, What Exactly Is React Native?

At its heart, React Native is a framework for building native mobile apps using JavaScript and React. It doesn’t run your code in a browser like a standard web app. Instead, it uses a “bridge” to communicate with the native platform’s APIs.

When you write a <View> or <Text> component in React Native, it doesn't render an HTML div or p. Instead, it renders a native UIView on iOS and an android.view.View on Android. This is crucial! It's why React Native apps feel and perform like native apps – because, at the UI layer, they are native apps.

You get to leverage the component-based architecture of React that many of us already know and love from web development. Build small, reusable pieces of UI and compose them to create complex screens. It’s intuitive, efficient, and makes managing your codebase much easier.

Why Would You Choose React Native? (Spoiler: Lots of Good Reasons!)

Okay, let’s get into the “why.” Why is React Native so popular?

Cross-Platform Magic (Almost!): This is the big one. Write most of your code once and deploy to both iOS and Android. This drastically cuts down development time, effort, and cost. While you might occasionally need a tiny bit of platform-specific code, the vast majority is shared.
Code Reusability: Not only between platforms but potentially between your web and mobile apps if you’re already using React on the web! You can share logic, state management, and sometimes even UI components (though native UI components often differ slightly).
Native Performance: As we touched on, it renders native components. This means smooth animations, fast scrolling, and a responsive feel that’s hard to achieve with purely web-based solutions. The JavaScript runs in its own thread, separate from the UI thread, so expensive calculations don’t block your user interface.
Hot Reloading & Fast Refresh: Oh boy, talk about developer happiness! Make a change in your code and boom, see it reflected in your app almost instantly without losing the current state. This rapid feedback loop makes development incredibly fast and enjoyable.
Huge Community & Ecosystem: React Native is backed by Facebook (now Meta) and has a massive, active community. This means tons of libraries, tools, tutorials, and forums where you can find help when you’re stuck. If you need a specific feature, chances are someone has already built a library for it.
Leverage JavaScript/React Skills: If you’re already a React web developer, you have a massive head start! The core concepts of components, state, props, and JSX are the same. You just need to learn the React Native specific components and APIs.
Cost-Effective: Fewer developers needed for two platforms, faster development cycles — it all adds up to significant cost savings compared to building natively for both.

The Core React Native Tech Stack: The Essentials

Alright, let’s pop the hood and look at the foundational pieces you’ll definitely be working with:

React: Yep, the OG JavaScript library for building user interfaces. React Native uses React’s declarative paradigm, component model, and JSX syntax. You’ll be thinking in terms of components just like on the web.
JavaScript (or TypeScript): This is your primary language. JavaScript is flexible and widely used. However, for larger or more complex apps, most developers highly recommend using TypeScript. TypeScript adds static typing to JavaScript, which helps catch errors early, improves code maintainability, and makes refactoring a breeze. It’s a lifesaver, seriously.
React Native CLI or Expo: How do you actually start a React Native project? You have two main paths:

React Native CLI: This is the more traditional approach. It gives you full control over your native projects (the iOS and Android folders). You’ll need a bit more setup (Xcode for iOS, Android Studio for Android) and knowledge of native build processes. You have direct access to native modules and can easily link third-party libraries that have native code.
Expo: This is fantastic for getting started quickly and for many types of apps. Expo provides a managed workflow that abstracts away a lot of the native complexity. You don’t even need Xcode or Android Studio installed locally to build and run your app on devices or simulators. Expo provides a ton of built-in APIs for common device features (camera, location, notifications, etc.). The trade-off is that if you need a native module not included in the Expo SDK, you’ll need to “eject” from the managed workflow (which gives you the native folders, essentially switching to the CLI approach) or use Expo’s development client builds. For many projects, Expo is more than enough and makes life so much easier.

Native Modules & Components: While you write mostly JavaScript, sometimes you need to access a specific native feature or use a performance-critical native library. React Native provides a way to write native modules (in Objective-C/Swift for iOS, Java/Kotlin for Android) and expose them to your JavaScript code. Similarly, you can wrap existing native UI components to use them within your React Native app. This “bridge” is key to React Native’s power.

Beyond the Core: Common Libraries & Tools You’ll Encounter

Once you’ve got the basics down, you’ll quickly find yourself reaching for libraries to handle common tasks. The React Native ecosystem is rich!

Navigation: Mobile apps need navigation! How do you go from one screen to another? The de facto standard is React Navigation. It’s flexible, highly customizable, and handles common navigation patterns like stacks, tabs, and drawers beautifully.
State Management: As your app grows, managing data and how it changes (state) becomes crucial. While React’s built-in useState and useContext hooks are great for local and simple global state, for larger apps, you'll likely consider:

Redux / RTK (Redux Toolkit): A predictable state container. Can be a bit boilerplate-heavy, but Redux Toolkit simplifies things greatly.
MobX: Another popular option, often considered more flexible and less boilerplate-heavy than classic Redux.
Context API + Hooks: For medium-sized apps or specific features, using React’s built-in Context API with useContext and useReducer can be sufficient and avoids external libraries.
Zustand / Jotai: More modern, lightweight state management libraries that are gaining popularity.

Styling: How do you make your app look good?

StyleSheet.create: React Native's built-in way to define styles. It's similar to CSS but uses JavaScript objects. Recommended for performance.
Styled Components / Emotion: Popular libraries from the web that you can also use in React Native for styling components with tagged template literals.
NativeBase / Tamagui: UI component libraries that provide pre-built, styled components you can use to build your UI faster. Tamagui is particularly interesting for its universal styling capabilities between web and native.

Making API Calls: Your app will likely need to fetch data from a server.

Fetch API: Built into JavaScript, simple for basic requests.
Axios: A popular promise-based HTTP client with more features like interceptors.
React Query / SWR: Data fetching libraries that handle caching, background updates, and error handling automatically, making your life much easier for complex data interactions.

Testing: You want to make sure your app works correctly!

Jest: A JavaScript testing framework often used for unit and integration tests.
React Native Testing Library: Provides utilities for testing React Native components in a way that resembles how users interact with your app.
Detox / Appium: End-to-end testing frameworks that run your app on a simulator or device and interact with it like a user would.

Accessing Device Features: You’ll need libraries to use the camera, access the file system, get the user’s location, send notifications, etc. Expo provides many of these out of the box. If you’re using the bare React Native CLI, you’ll find dedicated community libraries for almost everything (e.g., react-native-camera, react-native-geolocation-service).
Build & Deployment: Getting your app onto the App Store and Google Play.

Manual Processes: Using Xcode and Android Studio directly.
Fastlane: Automates building and releasing mobile apps.
App Center / Expo Application Services (EAS): Cloud-based services for building, testing, and distributing your apps. EAS is Expo’s integrated solution and is fantastic if you’re in the Expo ecosystem.

Developer Experience: Making the Journey Smoother

Beyond the core code, there are tools that make developing with React Native a joy:

VS Code Extensions: Many excellent extensions for syntax highlighting, autocompletion, debugging, and linting specifically for React Native and TypeScript.
React Native Debugger: A standalone app that combines Redux DevTools, React DevTools, and the Chrome debugger into one handy window.
Flipper: A desktop debugging platform for mobile apps, including React Native, allowing you to inspect network requests, view logs, examine layout, and more.

Any Gotchas? (Keep it Real!)

While React Native is amazing, it’s not a magic wand that eliminates all problems. You might occasionally run into:

Native Module Compatibility: Sometimes a library’s native code might not work perfectly on both platforms or require specific linking steps (less common with auto-linking now, but still possible).
Platform-Specific Differences: While the goal is shared code, sometimes UI or behavior needs slight adjustments for iOS vs. Android (e.g., navigation header appearance, specific gestures).
Performance Optimization: For very complex animations or heavy computation, you might need to profile and potentially drop down to native code or use libraries optimized for performance.
Upgrades: Upgrading React Native or libraries can occasionally be tricky, though it has improved loads over the years.

But honestly? The benefits far outweigh these potential hurdles for most projects.

Wrapping It Up!

Phew! We covered a lot, didn’t we? React Native, with its powerful tech stack powered by React and JavaScript, offers a fantastic way to build high-quality, performant mobile applications for both iOS and Android without doubling your workload.

You get the speed and iteration of web development combined with the look and feel of native apps. The ecosystem is vibrant, the community is supportive, and the developer experience, especially with tools like Fast Refresh and Expo, is truly top-notch.

If you’re looking to build mobile apps efficiently and effectively, seriously consider giving React Native a whirl. It’s a powerful tool that can unlock incredible possibilities for you and your projects.

Happy coding, and maybe I’ll see your awesome app on the app stores built with React Native!