Most small and mid-sized businesses can't afford to build two separate mobile apps. One team for Android, another for iOS, two codebases to patch every time something breaks — it's expensive and honestly a bit wasteful for a local bakery app or a neighbourhood salon's booking system. That's the practical reason React Native caught on the way it did: write the logic once in JavaScript, ship it to both platforms, and spend the time you saved on actually making the app good instead of maintaining two of everything.
Devmixa is a small web design and digital marketing team based in Bhopal, and we've been building exactly this kind of app for clients for a while now — local business apps, appointment and booking tools, small e-commerce storefronts that need to work smoothly on a customer's phone without draining their battery or data plan. We're opening our first dedicated seat for this work in Lucknow, based out of Gomti Nagar, because a few of our newer clients are based in and around UP and it made sense to have someone closer to them.
What you'd actually be building
This isn't a role where you sit and write boilerplate all day. Over the last year our mobile projects have included a booking app for a chain of salons, a simple ordering app for a regional sweets and snacks brand, and an internal logistics tracker for a client who runs a small fleet of delivery vehicles. Each one needed different things — push notifications so a salon's customers don't forget their appointment, API integration with a payment gateway for the ordering app, and offline-friendly data handling for the logistics tool since drivers don't always have good signal.
You'll be expected to pick up a Figma design and turn it into working screens, hook those screens up to backend APIs (mostly REST, sometimes GraphQL depending on the client), and care about how the app actually feels — load times, smooth scrolling, animations that don't stutter on a budget Android phone. A lot of our users are on mid-range devices, not the latest iPhone, so performance isn't optional here.
Day to day, this looks like:
- Building and maintaining screens and components using React Native, using Expo where it fits and bare workflow when a client needs a native module we can't avoid
- Managing state with Redux or Context API depending on how complex the app's data flow is
- Wiring up REST APIs, handling auth tokens, and dealing with the inevitable edge cases when an API returns something unexpected
- Setting up push notifications, testing them on actual Android and iOS devices, not just the simulator
- Working with our design and backend folks to figure out what's realistic to build in the time a client's budget allows
- Testing builds on real phones before anything goes to the client — we don't ship untested mobile builds, ever
Why Gomti Nagar, and why now
Gomti Nagar has become one of the more active pockets for IT and service companies in Lucknow over the past few years — it's not Hitec City or Gurugram, but there's enough happening here that a developer doesn't need to relocate to Bangalore just to find decent mobile development work. Rent is manageable, commute is easy if you're anywhere in Lucknow, and honestly for a lot of candidates we talk to, being able to build a real career without leaving Uttar Pradesh matters a lot. That's part of why we're setting up here instead of just hiring remote.
The role is on-site. We know remote work is common in tech now, but at this stage we want the team sitting together, at least for this first hire in the city — pairing on a tricky bug, reviewing a pull request together on one screen, that kind of thing is just faster in person when you're building something new.
Who fits this role
We're hiring across two bands here. If you're a fresher — recent graduate, maybe you've built a couple of personal or college projects using React Native or even just React JS and want to go mobile — we're genuinely open to that. The starting salary for a fresher is ₹18,000 to ₹25,000 a month, and it's structured to grow fast once you show you can own a feature end to end. For someone with 2 to 4 years of relevant experience, the range runs ₹35,000 to ₹58,000 a month, roughly ₹3.5 to ₹7 LPA, depending on what you bring — TypeScript experience, exposure to native Android or iOS development, or prior work shipping apps that are actually live on the Play Store or App Store.
What matters more than years on a resume is whether you can actually debug a layout issue that only shows up on one specific Android device, or figure out why an API call works on Wi-Fi but fails on mobile data. That's the real job, and it's taught more by doing than by any certificate.
Skills we're looking for
- Solid JavaScript fundamentals — this matters more than people expect, no framework fixes weak JS basics
- Working knowledge of React JS and how component-based UI thinking applies to mobile screens
- Comfort with Redux, Context API, or similar state management approaches
- Exposure to Expo for faster builds, and at least a conceptual understanding of when you'd need to eject to bare workflow
- Basic understanding of how Android and iOS differ — permissions, build processes, app store requirements
- Experience with API integration and handling asynchronous data properly
- Bonus: TypeScript, since we're slowly migrating our codebases toward it
- Bonus: any hybrid app development experience outside the usual stack, just shows you understand the tradeoffs
If you're a fresher reading this and wondering whether you even stand a chance against someone with experience — we built this fresher band specifically because we've hired people before who learned fast once they were actually working on live client apps rather than tutorials. A good GitHub profile with two or three complete mobile projects, even small ones, tells us more than a degree does.
How we actually work
We're a small team, which means less bureaucracy but also less hand-holding. You'll get a proper onboarding on our codebase and tools in the first week, then you're expected to start owning small pieces of real client work within the first month. Code reviews happen on every pull request — not as a formality, but because catching a memory leak or a bad re-render before it ships saves everyone a headache later.
We use Git for version control, Figma for design handoff, and a mix of Jira and simple shared docs for tracking tasks depending on the client. Nothing exotic, nothing you'll need to relearn from scratch if you've worked in any reasonably organized dev team before.
Growth path
This is an individual contributor role to start, but Devmixa is still a small, growing company, which means the person who takes this seat early has a real shot at becoming the senior mobile person on the team as we take on more app projects out of Lucknow. We're not promising a title on day one — we're being upfront that the path exists if you're good and you stick around.
Salary reviews happen based on actual contribution, not just tenure. Someone who ships three solid features and fixes production bugs without hand-holding will move up the pay band faster than someone who just shows up for two years. That's the honest version of how it works here, and we'd rather be upfront about it than promise something vague.
What we need from you to apply
Send across your resume along with links to any apps you've built — even a personal project on your phone that you can screen-record and share counts. If you've published anything to the Play Store or TestFlight, link it. We'll shortlist based on actual work shown, not just keywords on a resume, and we'll call shortlisted candidates for either an in-person interview or a short walk-in session at our Gomti Nagar office, depending on scheduling.
We'd rather see a rough, working app you built on a weekend than a perfectly worded resume with no projects attached. If you've got questions about the role before applying, feel free to reach out directly — we'd much rather clear things up upfront than have someone show up to an interview unsure of what the job actually involves.