Ways I can contribute.
The same kind of application work I do at MT Pixels: Angular and Next.js interfaces for orders, accounts, and field operations.
01Web applicationsThe work is stuck in spreadsheets, inboxes, or a tool that was never built for this process.
Detail
I build the product in Angular, React, or Next.js with TypeScript: the flows people use, and the API calls those flows depend on.
A web application people can run: orders, accounts, field operations, reporting, or the public pages beside them.
This is the work I do at MT Pixels. Remote projects start from a short written note about the problem.
02API-backed interfacesThe screens are not the system of record. Orders, users, and payments already live behind an API.
Detail
I build the TypeScript interface against that API. In Angular that is a service contract per feature. In Next.js it is one API client. Sign-in, where the product needs it, becomes an application session before those calls open.
Screens that stay in step with the API they call, with the roles and forms the workflow needs.
This is how the MT Pixels applications on this site are built. The same kind of interface work is what I take remotely.
03Product deliveryThe product has a real workflow, and it needs to ship as software people can use every day.
Detail
I carry it from the roles and the data through review and debugging, until that workflow runs as software.
An application for that workflow, reviewed and debugged as it goes out.
Onsite in Karachi at MT Pixels, and the same kind of work remotely.