Lenny Daume
Start a conversation
dtms GmbH Logo

dtms GmbH

Hamburg

Mobile Device Management System

Software Developer Enterprise Java

July 2012 - November 2012
5 months
Full-time
Product work
Hamburg

Relevance

Why this case matters

The case shows how problem understanding, responsibility, decisions, and implementation came together in this context.

Impact

Built a complete enterprise mobile-device platform from problem definition through iOS/Java implementation and multi-channel messaging to production application support.

What carries forward today

The case shows early production-near systems work: product problem, mobile client, backend, integrations, delivery, and application support as one system, with dedicated administrators owning infrastructure and databases.

Enterprise iOSMobile backendMDMEnd-to-End DeliveryProduction SupportScrumCI

Defensible proof

End-to-end

Mobile-device platform

Connected problem definition, product and architecture decisions, implementation, delivery, and production-near application support.

iOS + Java

Client and backend

Built the enterprise iOS application, Wicket/JAX-RS backend, persistence, and central administration.

Push + SMS + email

Messaging

Connected device, application, and user management with multiple notification channels.

Where this experience creates value

  • For enterprise products that need mobile clients, backend, device management, and messaging connected reliably.
  • For teams that want complete product responsibility made visible in classic Java/iOS environments.

Case context

Overview

Enterprise mobile device administration needed device management, app management, user management, and messaging in one system. I built the platform from problem definition through product and architecture decisions, iOS and Java implementation, delivery, and production-near application support. Changes were sometimes made directly in production, while dedicated administrators retained responsibility for servers and databases. The workflows connected Apple Push Notifications, email, SMS capabilities, and a Java backend.

The system included an enterprise iOS application for iPhone, iPad, and iPod Touch, compatible with iOS versions 4.3 through 6.0. Built with a Java 7 backend using Apache Wicket 6.3.0, JPA/Hibernate, and Jersey JAX-RS, the solution enabled centralized app distribution, device management, and user notification workflows.

Responsibility

Activities

  • MDM System Development: Device management, app management, user management, centralized mobile administration
  • Enterprise iOS App Development: iPhone/iPad/iPod Touch app, iOS 4.3-6 compatibility, Objective-C/Xcode development
  • Messaging System Integration: Apple Push Notifications, email notifications, SMS alerts, multi-channel communication
  • Backend Architecture: Java 7, Apache Wicket 6.3.0, JPA/Hibernate, Jersey JAX-RS, MySQL database
  • Agile Development: Scrum methodology, iterative delivery, continuous integration, quality assurance
  • End-to-End Delivery: Problem definition, product and architecture decisions, implementation, delivery, and production-near application support in collaboration with administrators

Operating mode

Methodology

  • Scrum Framework: Agile development, sprint planning, iterative delivery, continuous improvement
  • Full-Stack Development: Backend Java development, iOS Objective-C development, integrated system architecture
  • Enterprise Integration: Apple Push Notifications, multi-channel messaging, centralized device management
  • Quality Assurance: Comprehensive testing, code quality validation, enterprise-grade reliability

Technical context

Technology stack

The tools are not the point by themselves. What matters is which system layers had to work together.

8Areas
22Technologies

Backend

7
Java 7Apache Wicket 6.3.0JPAHibernateGoogle GuiceJersey JAX-RSEnterprise Java Development

Frontend

1
JavaScript

Mobile

5
iOSObjective-CXcodeApple Push NotificationsEnterprise iOS Development

Databases & Storage

1
MySQL

DevOps

2
TomcatMaven

Tools

4
TestNGCheckstylePMDFindbugs

CI/CD & Delivery Pipelines

1
Jenkins

Practices

1
Scrum

Next step

If you need similar responsibility, we can identify the next useful leverage point directly.

Send the situation, goal, and decision in front of you. I will respond personally with a clear view of the value I could add.

Discuss the next leverage point