Android模块化实战：除了页面跳转，ARouter的拦截器与服务发现还能这样玩？

Android模块化进阶ARouter拦截器与服务发现的深度实践在大型Android应用开发中模块化架构已经成为提升团队协作效率和代码可维护性的关键策略。而ARouter作为阿里巴巴开源的优秀路由框架其价值远不止于简单的页面跳转。本文将深入探讨ARouter的拦截器机制和服务发现功能展示它们如何成为模块化架构中的中枢神经。1. 拦截器机制不只是权限检查ARouter的拦截器(IInterceptor)是其最强大的功能之一它允许开发者在路由跳转过程中插入自定义逻辑。虽然最常见的用法是登录验证但拦截器的潜力远不止于此。1.1 拦截器的核心原理ARouter的拦截器基于责任链模式实现每个拦截器都有优先级(priority)属性。当调用navigation()方法时ARouter会按照优先级顺序依次执行拦截器链Interceptor(priority 10) public class AuthInterceptor implements IInterceptor { Override public void process(Postcard postcard, InterceptorCallback callback) { // 拦截逻辑实现 if (needAuth(postcard) !isLogin()) { callback.onInterrupt(new RuntimeException(未登录)); } else { callback.onContinue(postcard); } } Override public void init(Context context) { // 初始化工作 } }关键点优先级数字越小执行越早必须调用callback.onContinue()或onInterrupt()否则流程会中断init()方法只会在首次使用时调用一次1.2 高级应用场景AB测试分流根据用户分组动态路由到不同页面Interceptor(priority 20) public class ABTestInterceptor implements IInterceptor { Override public void process(Postcard postcard, InterceptorCallback callback) { if (isABTestPage(postcard)) { String newPath getVariantPath(postcard); postcard.setPath(newPath); } callback.onContinue(postcard); } }性能监控记录页面跳转耗时Interceptor(priority 100) // 低优先级最后执行 public class PerformanceInterceptor implements IInterceptor { Override public void process(Postcard postcard, InterceptorCallback callback) { long startTime System.currentTimeMillis(); callback.onContinue(postcard); long cost System.currentTimeMillis() - startTime; logPerformance(postcard.getPath(), cost); } }动态特性开关根据服务端配置禁用特定功能入口2. 服务发现模块间通信的优雅方案ARouter的服务发现机制(IProvider)提供了一种类型安全的模块间通信方式完美解决了模块化架构中的服务调用问题。2.1 基础用法回顾定义一个服务接口和实现public interface PaymentService extends IProvider { void pay(String orderId, double amount); } Route(path /service/payment) public class PaymentServiceImpl implements PaymentService { Override public void pay(String orderId, double amount) { // 支付逻辑实现 } Override public void init(Context context) { // 初始化逻辑 } }使用服务// 方式一依赖注入 Autowired(name /service/payment) PaymentService paymentService; // 方式二动态获取 PaymentService service (PaymentService) ARouter.getInstance() .build(/service/payment) .navigation();2.2 高级应用模式多实现服务路由根据不同场景选择不同实现Route(path /service/logger/debug) public class DebugLogger implements LoggerService { // 调试版日志实现 } Route(path /service/logger/release) public class ReleaseLogger implements LoggerService { // 正式版日志实现 } // 根据BuildConfig选择实现 String path BuildConfig.DEBUG ? /service/logger/debug : /service/logger/release; LoggerService logger (LoggerService) ARouter.getInstance() .build(path) .navigation();服务降级主实现不可用时使用备用方案public class DegradePaymentService implements PaymentService { // 降级实现 } PaymentService service; try { service (PaymentService) ARouter.getInstance() .build(/service/payment) .navigation(); if (service null) throw new RuntimeException(); } catch (Exception e) { service new DegradePaymentService(); }跨进程服务结合AIDL实现进程间通信3. 拦截器与服务发现的协同应用将拦截器和服务发现结合使用可以构建更加灵活的模块化架构。3.1 权限校验服务化将权限检查逻辑封装为服务供拦截器调用Route(path /service/permission) public class PermissionServiceImpl implements PermissionService { Override public boolean checkPermission(String permission) { // 权限检查逻辑 } } Interceptor(priority 10) public class PermissionInterceptor implements IInterceptor { private PermissionService permissionService; Override public void init(Context context) { permissionService (PermissionService) ARouter.getInstance() .build(/service/permission) .navigation(); } Override public void process(Postcard postcard, InterceptorCallback callback) { if (needPermissionCheck(postcard)) { String requiredPermission getRequiredPermission(postcard); if (permissionService.checkPermission(requiredPermission)) { callback.onContinue(postcard); } else { callback.onInterrupt(new RuntimeException(权限不足)); } } else { callback.onContinue(postcard); } } }3.2 动态路由决策根据业务状态动态决定路由目标Route(path /service/router) public class RouterServiceImpl implements RouterService { Override public String decideTarget(String originalPath) { // 根据业务规则返回实际路径 if (isNewUser() originalPath.equals(/home)) { return /home/newuser; } return originalPath; } } Interceptor(priority 5) // 高优先级最先执行 public class DynamicRouterInterceptor implements IInterceptor { private RouterService routerService; Override public void init(Context context) { routerService (RouterService) ARouter.getInstance() .build(/service/router) .navigation(); } Override public void process(Postcard postcard, InterceptorCallback callback) { String newPath routerService.decideTarget(postcard.getPath()); if (!newPath.equals(postcard.getPath())) { postcard.setPath(newPath); } callback.onContinue(postcard); } }4. 性能优化与最佳实践4.1 拦截器性能优化懒加载在init()中只做必要初始化优先级规划避免高优先级拦截器执行耗时操作缓存策略对重复检查结果进行缓存Interceptor(priority 10) public class CacheableAuthInterceptor implements IInterceptor { private AuthService authService; private LruCacheString, Boolean authCache; Override public void init(Context context) { authService (AuthService) ARouter.getInstance() .build(/service/auth) .navigation(); authCache new LruCache(100); } Override public void process(Postcard postcard, InterceptorCallback callback) { String cacheKey postcard.getPath(); Boolean cached authCache.get(cacheKey); if (cached ! null) { if (cached) callback.onContinue(postcard); else callback.onInterrupt(new RuntimeException(未授权)); return; } boolean authorized authService.checkAuth(postcard); authCache.put(cacheKey, authorized); if (authorized) callback.onContinue(postcard); else callback.onInterrupt(new RuntimeException(未授权)); } }4.2 服务发现的最佳实践接口设计原则保持接口简洁避免频繁变更明确线程模型实现类注意事项避免在init()中执行耗时操作处理好生命周期考虑内存泄漏问题服务调用规范对可能为null的服务做防御性判断考虑添加超时机制记录服务调用日志public interface TimeoutService extends IProvider { Timeout(5000) // 自定义注解表示超时时间 Response callWithTimeout(Request request); } // 调用方实现 try { Response response service.callWithTimeout(request); } catch (TimeoutException e) { // 处理超时 }4.3 调试与监控拦截器链可视化打印执行的拦截器顺序服务依赖分析生成服务调用关系图性能监控记录服务调用耗时// 调试工具类示例 public class ARouterDebugger { public static void printInterceptors(Postcard postcard) { ListIInterceptor interceptors ARouter.getInstance() .getInterceptorService() .getInterceptors(); for (IInterceptor interceptor : interceptors) { Log.d(ARouterDebug, Interceptor: interceptor.getClass().getSimpleName()); } } public static void printServiceDependencies() { // 通过反射获取ARouter内部的服务注册表 // 分析并打印服务间的依赖关系 } }在大型电商App的实际开发中我们通过ARouter的拦截器实现了统一的支付权限检查、AB测试分流和页面性能监控。服务发现机制则帮助我们解耦了用户系统、支付系统和推荐系统等核心模块。当App模块数量超过20个时这套架构依然保持了良好的可维护性和扩展性。