Skip to content
Muhammet Şafak
tr

Expertise

JavaScript and TypeScript developer — web and mobile fed by one API

Shipping the same feature across three layers — a Laravel API, a web UI and a React Native app — taught me the hard part is the contract, not the code.

years
18

My identity in this ecosystem fits in one sentence: the person who writes a product’s back end and sets its web and mobile surfaces on the same contract. I do not build design systems; I build the interface that talks to the API. JavaScript and TypeScript are not a preference on this page but the language of the layer where the product touches the user.

When I delivered the same feature as an API, a web interface and a mobile app, all three at once, I saw that the hard part of the work was not code but the contract. That is why I use TypeScript: end-to-end type safety from the API to the interface. I worked on Vue for a long time; today the weight is on React because mobile work calls for React Native.

The tools keep changing; I moved from jQuery and AJAX to Gulp, to Webpack, to Vite, and what I paid at every move was the same: configuration. I take a new tool only if it gives back more than that bill. The parts of interface architecture that touch the system side I write about in the Engineering section.

What is JavaScript?

JavaScript is the language of the browser and also runs on Node.js, a JavaScript runtime; TypeScript adds static types to it. A JavaScript and TypeScript developer writes web interfaces, mobile apps and build pipelines in them.

What do I do with JavaScript?

I am on the side that writes a product's back end and sets its web and mobile surfaces on the same REST API contract: React for the web interface, React Native and Expo for the mobile client, TypeScript for one contract from API to interface, Vite and Tailwind CSS for the build and style pipeline. I do not build design systems; I build the interface that talks to the API.

Recent writing in this area

Technologies I pair it with

  • TypeScript

    The type layer that carries one contract from API to UI.

  • React

    The component side.

  • React Native

    The iOS and Android half of the same product.

  • Expo

    Builds, store submission and OTA updates.

  • Vite

    The build pipeline that cut dev server startup to seconds.

  • Tailwind CSS

    Utility-first styling layer.

  • Node.js

    Where the toolchain runs.

Frequently asked

9 questions

  • How long have you written JavaScript?

    Since 2008, so 18 years — the same year as PHP. The two were two faces of one job: PHP on the server, first jQuery and later Vue and React in the browser.

  • Are you a frontend developer?

    Not exactly. I am the person who writes the product's backend and then puts its web and mobile surfaces on the same contract. I am not the one building a design system from scratch; I am the one building the interface that talks to the API.

  • Vue or React?

    I have written both. On the Vue side about component architecture, routing and state management (Vuex, later Pinia); on the React side about hooks, concurrent rendering and the form actions that arrived with React 19. Today mobile work makes React Native mandatory, so the weight sits on the React side.

  • Do you build mobile apps?

    Yes, with React Native and Expo. I have written mobile clients that way, and getting them to the stores is part of the job. I have separate posts on OTA updates, navigation architecture and list rendering performance.

  • Do you use TypeScript?

    Yes, and the reason collapses into one thing: end-to-end type safety from API to UI. Writing the contract twice, once at each end, means there is no contract.

  • Doesn't the toolchain change constantly?

    It does, and I moved that chain from Gulp to Webpack and from Webpack to Vite myself. But every migration cost the same thing: configuration. Replacing a tool is only the right call if it returns more than the configuration bill you pay for it.

  • What does a JavaScript and TypeScript developer do?

    They write browser interfaces, mobile apps and the build pipeline in those languages. For me that means a web interface that talks to an API, a React Native client that uses the same API, and the TypeScript types that tie the two to one contract.

  • How do you feed web and mobile from the same API?

    By keeping the separation strict: web and mobile never talk to each other, only through the shared REST API. Most of the bugs I meet in the interface look like interface bugs and turn out to be contract bugs — a field name, a date format or the meaning of an error code that drifted apart between layers. So I start not from how the interface will look but from what the back end promises.

  • What do you not do?

    Accessibility audits, building design systems and advanced animation work are not my area, and I say so when it needs saying. The parts of interface architecture that touch the system side — rendering decisions, caching strategy — I write about in the Engineering section.

Let us work together

If you have work in this ecosystem, tell me what you are building and we will talk about how to build it.

Search the site

Start typing to search posts, projects and pages.

Esc to close Powered by Pagefind