Learning and development process for Mobile application companies: cross-platform pairing and keeping up with phone changes
Phones change every year, and a mobile company that stops learning ships things that break. Learning here has to cover two platforms, new system versions and the skills of testers and designers.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWhy learning and development process matters in mobile application companies
Mobile developers usually specialise in one platform and learn the next system version when a store deadline forces them to. Testers pick up new devices on the job. Designers learn what works on small screens through client complaints. No one has time, so the company pays for learning in late fixes.
A practical process sets aside a regular slot, pairs people across platforms, schedules time to study each new system version before it arrives and gives testers and designers learning goals too. The result is a team that is harder to stall and easier to grow.
How to set it up
1. List what each role must learn next
For each platform, testing and design, name two or three topics for the next six months, including upcoming system versions.
2. Pair across platforms
Match an Android and an iOS developer on a small shared feature once a month. Each explains their approach.
3. Hold a short weekly session
An hour for demos, review of a crash, or a new technique. Rotate the lead, including testers.
4. Reserve time for system updates
Add a week each quarter to read changes and test existing products, and tell clients in advance.
5. Record what was learnt
Keep notes and update the skill list so staffing decisions use what people now know.
Check these first
Before changing anything, find out what is true today. These take an afternoon and use your own records.
- Ask each developer which system change worried them most last year.
- Check whether any Android and iOS developer has ever paired on a task.
- See how testers learn about new devices and who decides the list.
- Look at the last release problem and ask what knowledge would have prevented it.
GullyHR can do this with you. Read how we approach learning and development process in general, or share your requirements and we will tell you where to start.
Questions owners ask
Start with reviewing code and small tasks beside a colleague, and let them build confidence before client work. Expect months, not weeks, for real fluency.
Yes, enough to know what is easy or hard on a phone. A joint session with developers on real devices often teaches more than any course.
Keep the weekly slot short, protect it from routine requests and schedule larger study time in quiet periods. Skipping it during every release leaves you with no learning at all.