Mobile computing personal statement example

Why do you want to study this course or subject?

The thing that pulled me towards mobile computing was noticing how differently people around me use the same device. My grandmother uses her phone for three things: calls, the bus timetable and photographs of the garden. My brother, who is nine, treats his tablet as a games console and will happily tap through any warning message. I use mine for revision timers, maps and messaging groups that never stop. One piece of hardware, three completely separate sets of assumptions about what it is for. Designing software that has to work for all of them, on a small screen, with an unreliable connection and a battery that is always nearly flat, strikes me as a genuinely difficult problem rather than a decorative one. My A level Computer Science course covers algorithms, data representation and networks, and I have enjoyed the parts where constraints matter: why a lookup table might beat recalculation, why latency is not the same as bandwidth. Mobile devices make those constraints visible. I want to study a degree that treats the phone as a proper computing platform, with its own operating system behaviour, sensors, security model and interface conventions, rather than as a thin window onto a website. I am also interested in how design decisions affect people who have no choice about using an app, such as a council service or a booking system. A degree combining software engineering with human-centred design and networking is what I am looking for, and mobile computing sits exactly at that junction.

How have your qualifications and studies helped you to prepare?

I am studying Maths, Computer Science and Geography at A level. Maths has been the most useful foundation: work on sequences, logarithms and probability has made algorithm complexity far easier to reason about, and the discipline of setting out a proof line by line has improved how I structure code. In Computer Science I am building my coursework project, a revision app that schedules question sets at widening intervals. Getting the scheduling logic correct on paper before writing any Kotlin was a decision I am glad I made, because my first attempt at storing progress locally had to be rewritten and the logic survived intact. Geography has been an unexpectedly good companion subject. Fieldwork on footfall in our town centre meant designing a recording sheet, worrying about sampling bias and then presenting data honestly, including the results that did not support what we expected. That experience of gathering messy real-world data changed how I think about the sensor readings a phone produces. Outside lessons I completed an online course on Android development over last summer, working through layouts, activity lifecycle and saving data, and I have read parts of Don Norman's The Design of Everyday Things, which gave me vocabulary for something I had only sensed before: that if a user cannot tell what an interface will do next, the fault lies with the design. I have also started using version control properly, mostly because I lost an afternoon's work once and did not want to repeat it.

What else have you done to prepare outside of education, and why are these experiences useful?

Two afternoons a week I collect my brother from school and look after him until my mother finishes her shift, which means cooking, homework supervision and negotiating over screen time. It has made me reliable with a timetable and taught me how to explain something three different ways when the first two do not land. He was also my first honest tester: he found a button in my revision app that did nothing, within about forty seconds, because he pressed everything. I now hand anything I build to someone who has not seen it before. On Saturday mornings I volunteer at a community reading session at our local library, setting out books, reading with younger children and helping tidy afterwards. Occasionally I help older visitors with the public computers or with a phone that has updated itself into unfamiliarity. I have learned not to take the device out of someone's hands, and to describe where to tap rather than doing it for them. That patience feels closely connected to the kind of software I would like to make. I also play in a local badminton club league, which gives me a fixed commitment away from a screen and some practice at losing gracefully. For my own interest I built a small app that tracks my brother's football fixtures and sends a reminder the evening before, which forced me to learn about notifications and about storing dates sensibly. None of these things are grand, but together they have given me a working habit of finishing what I start and testing it on real people.

This example has 4,528 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.

Review this personal statement

Latest reviews